The agent produces one integrated plan across seven components: ICP, beachhead, motion, channels, messaging, metrics and launch sequence. Each choice has to fit the others; most stalled launches fail at a seam (a sales-led motion on a $4K ACV, channels with no budget, a message nobody tested).
Done looks like: an ICP specific enough to build a list from, and one beachhead inside it; a motion that fits the ACV; 2-4 channels, each with budget and an owner; a hero message under 120 characters that names the differentiator and was tested with ICP buyers; 3-6 metrics with targets and owners; three or more lighthouse customers before launch; gtm_strategy_validator.py exits 0 with no warnings left unanswered.
Build the ICP itself with project-management/gtm/ideal-customer-profile; this skill starts from it.
Before building the GTM strategy, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.
Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.
# Mid-market sales-led launch: exit 0, no findings
python3 project-management/gtm/gtm-strategy/scripts/gtm_strategy_validator.py \
--input project-management/gtm/gtm-strategy/assets/sample_gtm.json --format markdown
# "Everyone" ICP, sales-led at $4K ACV, seven unfunded channels, no metrics: exit 1
python3 project-management/gtm/gtm-strategy/scripts/gtm_strategy_validator.py \
--input project-management/gtm/gtm-strategy/assets/sample_gtm_flawed.json --format markdown
# Input schema and flags
python3 project-management/gtm/gtm-strategy/scripts/gtm_strategy_validator.py --help
gtm_strategy_validator.py is the quality gate for this skill. What the validator checks: an ICP with size, vertical, role, job and trigger; a beachhead; motion-ACV fit (sales-led under $10K, PLG over $100K); 1-6 channels with budget and owners; a hero message that exists (fail otherwise), is short and avoids generic terms; the self-reported differentiator_named / tested_with_customers flags; metrics present (fail otherwise) with targets and owners; lighthouse customers; alignment and budget. It checks that the parts exist and fit each other; it cannot judge whether the strategy will work, and the boolean flags are only as honest as whoever set them.
Exit codes: 0 no fail findings · 1 at least one fail (no ICP, channels, hero message or metrics) · 2 unreadable file, invalid JSON or a top level that is not an object. JSON by default, --format markdown, --output FILE.
ideal-customer-profile (size, vertical, geography, role, job, trigger). If it would fit "everyone who manages people", stop and sharpen it first.references/gtm-components-deep.md (appendix).references/launch-sequence-playbook.md.--help; assets/sample_gtm.json is a complete example) and run the validator. It must pass with no fail findings; then verify that each warning is fixed or has a stated reason.For a stalling GTM, audit the current plan first and fix the first broken seam (ICP, motion fit, channels, message, metrics) before touching the next.
Mistake: A field-sales motion sells a $4K-a-year product.
Why it happens: The team copies the motion of a company it admires.
Instead: Pick the motion from ACV and buying complexity, and check CAC payback before hiring for it.
Mistake: Seven channels in the plan, none with budget or an owner.
Why it happens: Listing channels feels like coverage.
Instead: Fund 2-4 channels properly and name who runs each; the rest wait for evidence.
Mistake: "Ship and announce", with no lighthouse customers or sequence.
Why it happens: The launch date is fixed before the GTM work starts.
Instead: Work back from T-90 and secure three or more lighthouse customers before the announcement.
More with fixes: references/gtm-anti-patterns.md.
In Scope:
gtm_strategy_validator.py)Out of Scope:
project-management/gtm/ideal-customer-profile/)marketing/launch-strategy/)business-growth/pricing-strategy/)business-growth/revenue-operations/)project-management/execution/launch-playbook/)Important Caveats:
gtm_strategy_validator.py audits a hand-written JSON document. Flags such as specific_enough and tested_with_customers are self-reported.| File | Purpose |
|---|---|
scripts/gtm_strategy_validator.py | GTM plan audit |
assets/sample_gtm.json | Mid-market HR analytics launch; exits 0 |
assets/sample_gtm_flawed.json | Unfocused launch plan; exits 1 |
assets/gtm_strategy_template.md | Fill-in template |
project-management/gtm/ideal-customer-profile — ICP definitionproject-management/strategy-frameworks/business-model-canvas — model behind GTMmarketing/launch-strategy — marketing execution layerbusiness-growth/customer-success-manager — post-sale GTMc-level-advisor/cro-advisor — sales / revenue strategyc-level-advisor/cmo-advisor — marketing strategy