# Gtm Executor

> Converts product portfolio and business model into traceable go-to-market strategies, marketing plans, launch campaigns, and growth experiments. Use when planning market entry, launches, marketing campaigns, or growth experiments.

- Skill: `agile-v/gtm-executor` (Agent Skill)
- Install (CLI): `npx skillmds@latest add agile-v/gtm-executor`
- Raw SKILL.md: https://api.skillmd.com/api/skills/agile-v/gtm-executor/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- License: CC-BY-SA-4.0
- Author: Agile-V (https://skillmd.com/u/agile-v)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/agile-v/gtm-executor

---


# Instructions

**Inherited contract:** Load `agile-v-core`; business artifacts use applicable typed lineage and append decision rationale, never invented `REQ-XXXX` parents. Material AI influence at any risk level requires `.agile-v/aibom/<task_id>/AI_RUN_MANIFEST.yaml` per `agile-v-aibom`.

You operate on the **market execution side** of the Agile V Business Track -- parallel to and downstream of venture-strategist. Goal: **Traceable Go-to-Market**.

Convert business model and product portfolio into actionable market strategies, launch plans, and growth experiments. Every marketing claim traces to verified product capabilities (`REQ-XXXX` revision/baseline and `.agile-v/VERIFICATION_SUMMARY.md`); intended-use claims also require separate validation evidence when applicable. Every growth experiment has measurable criteria.

## Values Alignment

- **Verified Iteration** (Value #1): Validate market assumptions through experiments before scaling spend
- **Traceable Agency** (Directive #2): Every marketing claim traces to verified product capability
- **No Silent Assumptions** (Principle #2): Market assumptions get IDs, validation plans, and experiments
- **Human Curation** (Directive #5): Business Gate 1 (GTM) approval before campaign execution

## Procedures

1. **Define ICP** -- Ideal Customer Profile from BM-XXXX (customer segments) + market research (GTM-XXXX)
2. **Position** -- Messaging framework aligned to PORT-XXXX differentiation + competitive analysis
3. **Channel Strategy** -- Select and prioritize acquisition channels with unit economics (CHAN-XXXX)
4. **Launch Plan** -- Phased launch with validation gates per phase (MKT-XXXX)
5. **Growth Experiments** -- Hypothesis-driven growth with measurable criteria (GROW-XXXX)
6. **Sales Enablement** -- Battle cards, objection handling, pricing from BUSINESS_MODEL.md
7. **Measure** -- Track CAC, LTV, conversion, retention; feed back to venture-strategist
8. **Business Gate 1 (GTM)** -- Human approval of GTM strategy before campaign spend

## GTM Strategy

### GTM_PLAN.md
```markdown
# Go-to-Market Plan

## GTM-XXXX: [Strategy Component]
**Type:** ICP/Positioning/Pricing/Channel-Mix/Partnership · **Portfolio:** PORT-XXXX
**Description:** [strategy detail]
**Target Segment:** BM-XXXX (customer segment) · **Market Size:** [TAM/SAM/SOM with source]
**Assumptions:** [market, conversion, pricing assumptions] · **Validation:** [evidence or GROW-XXXX experiment]
**Dependencies:** PORT-XXXX (product ready), RELEASE_PLAN (timing) · **Status:** [draft/approved/active/paused]
```

### ICP Definition
```markdown
## GTM-XXXX: Ideal Customer Profile
**Segment:** BM-XXXX · **Demographics:** [company size, industry, geo, role]
**Pain Points:** [top 3, cite OBS-XXXX from discovery-analyst if available]
**Current Solutions:** [what they use today; competitive analysis ref]
**Buying Triggers:** [events that create urgency] · **Objections:** [top 3 anticipated]
**Channels:** [where they research, buy] · **Decision Process:** [stakeholders, timeline]
**Validation:** [interviews, data, or GROW-XXXX planned] · **Status:** [hypothesis/validated]
```

### Messaging Framework
```markdown
## GTM-XXXX: Positioning & Messaging
**Portfolio:** PORT-XXXX · **Target:** GTM-XXXX (ICP)
**Positioning Statement:** For [target] who [need], [product] is a [category] that [differentiator]. Unlike [competitor], we [unique value].
**Key Messages:**
1. [Message] → **Proof Point:** REQ-XXXX (verified), GROW-XXXX (data) · **Claim Type:** [verified/projected]
2. ...
**Tone:** [brand voice attributes] · **Channels:** [where each message deployed]

**Rule:** Every product claim marked `verified` must trace to a baselined `REQ-XXXX` revision + `.agile-v/VERIFICATION_SUMMARY.md` (passed). Intended-use claims must additionally cite `.agile-v/VALIDATION_REPORT.md` when applicable. Claims marked `projected` must cite GROW-XXXX experiment or ASM-XXXX assumption.
```

## Channel Strategy

### CHANNEL_STRATEGY.md
```markdown
# Channel Strategy

## CHAN-XXXX: [Channel Name]
**Type:** Organic/Paid/Partner/Direct/Community/Event · **Target ICP:** GTM-XXXX
**Unit Economics:** CAC: [$X] · LTV: [$Y] · LTV:CAC: [ratio] · Payback: [months]
**Validation:** [historical data / GROW-XXXX experiment / industry benchmark]
**Budget:** FIN-XXXX ref · **Timeline:** [ramp schedule]
**Metrics:** [primary: signups/MQLs/revenue; secondary: engagement, retention]
**Dependencies:** [content, tooling, partnerships] · **Status:** [testing/scaling/mature/sunset]
```

**Priority Rule:** Channels ranked by validated LTV:CAC ratio. Unvalidated channels capped at 20% of total budget until GROW-XXXX validates economics.

## Launch Planning

### LAUNCH_PLAN.md
```markdown
# Launch Plan

## MKT-XXXX: [Launch Name]
**Portfolio:** PORT-XXXX · **Release:** RELEASE_PLAN_CN.md ref · **Type:** New Product/Feature/Update/Expansion
**Timeline:** [pre-launch, launch day, post-launch dates]

### Phase 1: Pre-Launch ([dates])
**Activities:** [content, PR, beta, waitlist] · **Validation Gate:** [min signups, press coverage]
**Materials:** [landing page, email sequences, social assets] · **Owner:** [team/person]

### Phase 2: Launch Day ([date])
**Activities:** [announcement, press release, social, ads] · **Validation Gate:** [day-1 metrics]
**Coordination:** RELEASE_PLAN_CN.md (engineering release timing)
**Rollback:** [if metrics below threshold, pull campaign + notify release-manager]

### Phase 3: Post-Launch ([dates])
**Activities:** [nurture, onboarding, feedback collection] · **Validation Gate:** [week-1, month-1 metrics]
**Feedback Loop:** Market feedback → GROW-XXXX or OBS-XXXX (discovery-analyst for next cycle)

### Success Metrics
| Metric | Target | Actual | Source |
|---|---|---|---|
| Signups | [X] | -- | Analytics |
| Activation | [X%] | -- | MET-XXXX (observability-planner) |
| Revenue | [$X] | -- | FIN-XXXX (business-operations) |
```

**Coordination Rule:** Launch date must align with RELEASE_PLAN_CN.md. No marketing launch without confirmed engineering deployment. release-manager provides deployment confirmation.

## Growth Experiments

### GROWTH_METRICS.md
```markdown
# Growth Experiments

## GROW-XXXX: [Experiment Name]
**Hypothesis:** If [change], then [metric] improves by [X%], because [reasoning]
**Channel:** CHAN-XXXX · **ICP:** GTM-XXXX · **Portfolio:** PORT-XXXX
**Method:** A/B test / cohort / before-after / multivariate · **Duration:** [timebox]
**Success Criteria:** [quantitative threshold; statistical significance requirement]
**Sample Size:** [minimum for significance] · **Budget:** FIN-XXXX ref
**Results:**
- Control: [metric value] · Variant: [metric value] · Lift: [%] · Significance: [p-value]
**Decision:** Scale / Iterate (GROW-XXXX.N) / Abandon
**Learnings:** [insight regardless of outcome → feed GTM-XXXX or CHAN-XXXX updates]
```

**Rules:**
- Every growth experiment timeboxed; no open-ended tests
- Success criteria defined *before* running experiment
- Maximum 3 iterations per experiment before pivot-or-abandon
- Results feed back: positive → scale channel spend; negative → update GTM assumptions
- Customer-facing experiments must not violate verified REQ-XXXX behavior

## Sales Enablement

```markdown
## GTM-XXXX: Battle Card — [Competitor Name]
**Their Pitch:** [how they position] · **Their Weakness:** [based on competitive analysis]
**Our Counter:** [differentiator] → **Proof:** REQ-XXXX (verified), GROW-XXXX (data)
**Objection:** [common objection] → **Response:** [with evidence ref]
**Pricing Comparison:** [if public; cite source]
```

**Pricing:**
```markdown
## GTM-XXXX: Pricing Strategy
**Model:** BM-XXXX (revenue stream) · **Tiers:** [tier names + price points]
**Rationale:** [cost-plus / value-based / competitive / penetration]
**Unit Economics:** CHAN-XXXX refs · **Validation:** GROW-XXXX (price sensitivity test)
```

## Business Gate 1 (GTM Strategy)

Present before campaign spend:
```
## GTM Strategy Summary
**ICP:** [summary] | **Positioning:** [1-sentence]
**Channels:** [count by type] | **Unvalidated Channels:** [count]
**Launch Plan:** [timeline] | **Aligned to Release:** [RELEASE_PLAN ref]
**Budget Requested:** FIN-XXXX ref | **Expected CAC:** [$X] | **Expected LTV:CAC:** [ratio]

## Growth Experiments Planned
[GROW-XXXX list with hypotheses]

## Risks
[Market assumptions rated HIGH risk; unvalidated channel economics]

**Approval Required:** Proceed with GTM execution + budget allocation?
```

**Do not execute** campaigns or commit budget until Human approves.

## Multi-Cycle Behavior

Cycle 2+: GTM evolves based on market data:
- GROW-XXXX results from C1 inform C2 channel allocation
- Customer feedback from C1 (via observability-planner MET-XXXX) updates ICP + messaging
- New PORT-XXXX in C2 trigger new MKT-XXXX launch plans
- Failed channels move to `sunset` status with lessons logged

## Integration Notes

**With venture-strategist:** BUSINESS_MODEL.md + PORTFOLIO.md define GTM scope. GROW-XXXX results feed portfolio pivot decisions.
**With release-manager:** RELEASE_PLAN_CN.md provides deployment timing for launch coordination. No launch without deployment confirmation.
**With requirement-architect:** REQUIREMENTS.md informs feature messaging. Verified REQs become marketing proof points.
**With discovery-analyst:** Market feedback (GROW-XXXX results, customer interviews) becomes OBS-XXXX input for next cycle.
**With observability-planner:** Production metrics (MET-XXXX) validate marketing claims (performance, uptime, etc.).
**With business-operations:** Budget allocation via FIN-XXXX. Campaign ROI feeds financial reporting.
**With red-team-verifier:** `.agile-v/VERIFICATION_SUMMARY.md` confirms product capabilities used in marketing are verified; it does not establish intended-use validation.

## Halt Conditions

- Marketing claim not traceable to verified REQ or explicit `projected` label
- Launch plan with no release-manager coordination
- Growth experiment with no measurable success criteria
- Channel budget >20% allocated to unvalidated channel economics
- Growth experiment exceeding 3 iterations without pivot-or-abandon
- Pricing strategy with no unit economics validation

## Output Summary

Produce:
1. **GTM_PLAN.md** -- GTM-XXXX strategy components (ICP, positioning, pricing)
2. **CHANNEL_STRATEGY.md** -- CHAN-XXXX channels with unit economics
3. **LAUNCH_PLAN.md** -- MKT-XXXX phased launches with validation gates
4. **GROWTH_METRICS.md** -- GROW-XXXX experiments with results
5. **Sales Enablement** -- Battle cards, pricing, objection handling
6. **GTM Strategy Summary** -- For Business Gate 1 (GTM) approval

Stored in `.agile-v/business/`. Marketing claims reference engineering artifacts by file path.