From gtm-strategy
Transforms a messy business idea into structured GTM primitives: Product, ICP segments, value proposition, beachhead market, and channel strategy.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gtm-strategy:idea-to-icp [your product idea or context][your product idea or context]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Take a messy business idea and work through to structured GTM primitives: Product, ICP segments, value proposition, beachhead market, and channel strategy.
Take a messy business idea and work through to structured GTM primitives: Product, ICP segments, value proposition, beachhead market, and channel strategy.
These principles govern every phase. Never violate them.
Product → ICP → ValueProp → Beachhead → Channels
Never skip ahead. If the user jumps to channels before ICP exists, acknowledge their input, park it, and redirect: "Great channel instinct — let's nail down who you're reaching first, then we'll match channels to them."
Parse whatever the user gives you first. Only ask about critical gaps. A vague "SaaS for landlords" already yields: format=SaaS, stage=Idea, vertical-hint=real-estate. Don't ask what you can infer.
Infer aggressively, mark confidence. Say "I'm inferring X — correct me if wrong" rather than "What is X?" The flow should never block on a non-critical field.
Generate 3-5 ICP hypotheses. User selects/ranks 1-2. One becomes the beachhead — the segment you attack first. This is the critical strategic decision.
Align with Cantrip's existing system from src/lib/interview.ts:
| State | Meaning | Marker |
|---|---|---|
empty | No data | [ ] |
draft | Exists but thin | [~] |
refined | Solid, could be sharper | [+] |
confirmed | User approved | [✓] |
Show these inline throughout all outputs.
Each phase asks at most 2 questions. Prefer presenting options over open-ended questions. Never ask more than you need to proceed to the next gate.
Linear progression. Read each workflow file when entering that phase.
| Phase | Gate to Enter | Workflow File |
|---|---|---|
| 1. Product Extraction | Always first | workflows/01-product-extraction.md |
| 2. ICP Hypothesis | Product name + one-liner exist | workflows/02-icp-hypothesis.md |
| 3. Value Proposition | 1+ ICP segment confirmed | workflows/03-value-proposition.md |
| 4. Beachhead Selection | 2+ segments ranked | workflows/04-beachhead-selection.md |
| 5. Channel Strategy | Beachhead selected | workflows/05-channel-strategy.md |
| 6. Summary | All above complete | workflows/06-summary.md |
Skip rules:
If $ARGUMENTS is provided: Start Phase 1 extraction immediately. Read workflows/01-product-extraction.md and parse the user's input.
If no arguments: Ask:
Tell me about your product or business idea — whatever you have, even if it's rough. A sentence, a paragraph, a brain dump — all work.
Then proceed to Phase 1 when they respond.
All outputs map to existing Cantrip data models:
| Skill Output | Cantrip Model | Key Fields |
|---|---|---|
| Product | ProjectModel | name, description |
| ICP Segment | ICPModel | name, painPoints, jobsToBeDone, currentAlternatives, willingnessToPay, priority |
| Value Prop | ValuePropositionModel | framing, options (as MultiOptionCandidate[]) |
| Channel | SocialWebEntryModel | platform, name, relevanceScore |
| Completeness | interview.ts | Uses same empty / draft / refined / confirmed states |
Load these on-demand when entering the relevant phase:
references/domain-primitives.md — Condensed schemas for Product, ICPSegment, ValueProp, and key enumsreferences/icp-patterns.md — Common segments by vertical + decision trees for market_type and buying_modelreferences/channel-taxonomy.md — Full channel list with motion, tags, and best-for guidanceProvides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub ozten/skills