[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CT8P7KXC57GM062PECTSAE":3,"skill-same:01M6CT8P7KXC57GM062PECTSAE":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":46,"updatedAt":47,"install":48,"resources":60},"01M6CT8P7KXC57GM062PECTSAE","gtm-sprint",null,"Runs a 7, 14 or 21 day go-to-market (GTM) sprint: customer interviews, positioning, landing page and distribution, with go\u002Fno-go checkpoints. Use to test demand or launch an MVP.","vibbs\u002Fcompany-os","vibbs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7379149?v=4","01M6CT6M03CAS1H7RA89F3965B","Vibbs Dod","01M6CT6M4MY60C9FFQ3AAR2RSK",6,"MIT","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgtm-sprint\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32],"gtm sprint","go","customer","test","launch","status","plan","page","check","landing","use","Market","gate","positioning","2026-11-10 10:12:30",false,"---\nname: gtm-sprint\ndescription: \"Runs a 7, 14 or 21 day go-to-market (GTM) sprint: customer interviews, positioning, landing page and distribution, with go\u002Fno-go checkpoints. Use to test demand or launch an MVP.\"\nuser-invocable: true\nargument-hint: \"[plan | status | gate-check] [7 | 14 | 21]\"\n---\n\n# GTM Sprint\n\n## When to Use\n\n- Pre-product validation: \"Do people actually want this?\"\n- MVP launch: \"We built it, now how do we get users?\"\n- New market entry: \"We're expanding to a new segment\"\n- Repositioning: \"Our current positioning isn't working\"\n- Any time the user says: \"go to market\", \"GTM\", \"launch plan\", \"validate market\", \"find customers\"\n\n## Reference\n- **ID**: S-GRO-09\n- **Category**: Growth\n- **Inputs**: company.config.yaml, ICP artifact (or triggers creation), objective description\n- **Outputs**: GTM Sprint Plan artifact + GTM Sprint Report artifact -> artifacts\u002Fgrowth\u002F\n- **Used by**: Growth Agent\n- **Tool scripts**: .\u002Ftools\u002Fartifact\u002Fvalidate.sh\n\n## Purpose\n\nOrchestrates a time-boxed go-to-market sprint that sequences validation, commitment, launch, and distribution into a structured daily cadence with quantified decision gates. Unlike `\u002Fship` (which builds software) or `\u002Frapid-prototype` (which proves technical feasibility), `\u002Fgtm-sprint` validates **market demand** and builds **distribution** — no code required.\n\nInspired by the 100x GTM Playbook methodology: validate with interviews, secure commitments (LOIs), build launch assets, activate distribution channels, and measure traction — all within a fixed sprint window.\n\n## When NOT to Use\n\n- Building software features -> use `\u002Fship`\n- Technical proof-of-concept -> use `\u002Frapid-prototype`\n- Single-channel optimization -> use `\u002Fchannel-playbook` directly\n- Post-launch growth optimization -> use individual growth skills directly\n\n## What You Will See\n\n`\u002Fgtm-sprint plan 14` produces a plan like this (excerpt). Each day lists tasks, the skill to use and the output.\n\n```text\nGTM Sprint Plan: Acme Invoices, 14 days, stage: idea\n\nDay 0  Prep: lock ICP and outreach\n  - Finalize ICP (role, company size, budget, current workaround)\n  - Build a 100-name prospect list; book 15+ calls for Days 1-2\n  - Skill: icp-positioning        Output: ICP artifact, prospect list\nDay 1  Pain discovery: Mom-Test interviews (10+, 15 min each)\n  - Skill: customer-conversations prep mom-test\n  - Output: 10+ CONV- artifacts\nDay 2  Insights: synthesize pain data\n  - Skill: feedback-synthesizer   Output: Pain Matrix\n  Gate: Interview Volume (>= 15 completed)\n```\n\n`\u002Fgtm-sprint gate-check` evaluates one gate and tells you what to do next:\n\n```text\nGate: Interview Volume (Day 2)   Metric: completed interviews\nThreshold: >= 15   Actual: 11   Result: FAIL (advisory at stage idea)\nCorrective action: extend Days 1-2 by 1-2 days and increase outreach volume.\nAdjust the plan, override the gate, or pause the sprint?\n```\n\nAnswer with `adjust`, `override` or `pause`. Gates are advisory at `idea` stage and enforced at `growth` and `scale`.\n\n## Modes\n\n### Mode: `plan` (default)\n\nGenerates a personalized GTM Sprint Plan with daily tasks, decision gates, and skill sequencing.\n\n### Mode: `status`\n\nReviews progress against the active GTM Sprint Plan — checks completed tasks, gate metrics, and recommends adjustments.\n\n### Mode: `gate-check`\n\nEvaluates a specific decision gate and recommends corrective action if thresholds are not met.\n\n## Procedure\n\n### Phase 0: Context & Configuration\n\n1. **Load Context**\n   - Read `company.config.yaml` for company name, stage, product description\n   - Check `artifacts\u002Fproduct\u002F` for existing ICP artifact\n   - Check `artifacts\u002Fdecision-memos\u002F` for existing CONV- artifacts (interview count)\n   - Check `artifacts\u002Fgrowth\u002F` for existing positioning, landing page, channel playbooks\n\n2. **Sprint Configuration**\n\n   Ask the user for (with smart defaults):\n\n   | Parameter | Default | Options |\n   |-----------|---------|---------|\n   | Sprint duration | 14 days | 7 \u002F 14 \u002F 21 days |\n   | Start date | Today | Any date |\n   | Objective | From product description | Custom |\n   | Target LOIs | 5 | 3-10 |\n   | Target interviews | 20 | 10-30 |\n   | Target wait-list | 50 | 25-200 |\n\n   Stage-aware defaults:\n   - `idea`: 14 days, 20 interviews, 5 LOIs, 50 wait-list\n   - `mvp`: 7 days (validation done), 10 interviews, 3 LOIs, 100 wait-list\n   - `growth`: 7 days (repositioning sprint), 15 interviews, 5 LOIs, 200 wait-list\n\n3. **ICP Check**\n   - If no ICP artifact exists: inform the user — \"No ICP found. The sprint will begin with ICP definition (Day 0). Run `\u002Ficp-positioning` now, or we'll include it in the sprint plan.\"\n   - If ICP exists but is `draft`: note it needs validation through interviews\n\n### Phase 1: Generate Sprint Plan (Mode: `plan`)\n\n4. **Build Daily Task Schedule**\n\n   Generate a day-by-day plan adapted to the sprint duration. For a 14-day sprint:\n\n   #### Week 1: Validate & Commit (Days 0-6)\n\n   **Day 0 — Prep: Lock ICP & Outreach**\n   - Finalize ICP criteria (role, company size, budget, current workaround)\n   - Build prospect list (100 targets) — use LinkedIn, communities, competitor reviews\n   - Book 15+ discovery calls for Days 1-2\n   - *Skill*: `icp-positioning` (if no ICP exists)\n   - *Skill*: `customer-conversations prep cold-outreach`\n   - *Output*: ICP artifact (draft or updated), prospect list\n\n   **Day 1 — Pain Discovery: Mom-Test Interviews**\n   - Conduct 10+ Mom-Test interviews (15 min each)\n   - Record key quotes and $$ impact of each pain point\n   - Focus: current behavior, cost of status quo, workarounds tried\n   - *Skill*: `customer-conversations prep mom-test`\n   - *Skill*: `customer-conversations debrief` (after each call)\n   - *Output*: 10+ CONV- artifacts\n\n   **Day 2 — Insights: Synthesize Pain Data**\n   - Conduct remaining interviews (target: 20 total)\n   - Run feedback synthesis on all CONV- artifacts\n   - Produce Pain Matrix: themes clustered by $$ impact + urgency\n   - Rank themes, identify top 3 \"hair-on-fire\" problems\n   - *Skill*: `feedback-synthesizer` (with pain-matrix output)\n   - *Output*: Feedback report with Pain Matrix\n\n   **Day 3 — Refine: Sharpen MVP Scope**\n   - Map current workflow -> desired workflow for top pain\n   - Update MVP scope based on Day 2 insights\n   - Quantify time saved and cost saved per user\n   - Draft value proposition: \"We help X do Y, saving Z hours\u002Fweek\"\n   - *Skill*: `prd-writer` or update existing PRD\n   - *Output*: Updated PRD or mini-PRD (if pre-product)\n\n   **Day 4 — Commit: Secure Letters of Intent**\n   - Draft 1-page LOI template (problem, proposed solution, commitment level, timeline)\n   - Re-contact top 5 prospects from interviews\n   - Show prototype\u002Fmockup\u002Fdemo and request commitment\n   - Obtain verbal commitments or e-signatures\n   - *Output*: LOI artifacts (target: 5 signed)\n\n   **Day 5 — Narrative: Go Public**\n   - Write 1-sentence mission statement\n   - Write 2-paragraph vision statement\n   - Craft positioning: \"We help [X] do [Y] in [Z] seconds\"\n   - Publish first build-in-public post\n   - *Skill*: `positioning-messaging`\n   - *Skill*: `channel-playbook` (build-in-public arc)\n   - *Output*: Positioning artifact, first public post draft\n\n   **Day 6 — Gate Check: Week 1 Review**\n   - Review metrics: interviews completed, LOIs signed, wait-list size\n   - **Decision Gate 1**: Evaluate against thresholds (see Decision Gates below)\n   - Adjust Week 2 plan based on gate results\n   - *Output*: Week 1 status update\n\n   #### Week 2: Launch & Grow (Days 7-13)\n\n   **Day 7 — Launch Pad: Landing Page**\n   - Build landing page with top 3 pain quotes above the fold\n   - Embed email capture \u002F wait-list form\n   - Add Calendly or booking link for demos\n   - *Skill*: `landing-page-copy`\n   - *Output*: Landing page copy artifact (or deployed page)\n\n   **Day 8 — Lead Magnet: Field Report**\n   - Compile interview insights into a downloadable asset\n   - Format: \"Field Report\" PDF, industry brief, or data snapshot\n   - Gate the download behind email capture\n   - *Skill*: `content-engine` (lead-magnet format)\n   - *Output*: Lead magnet content artifact\n\n   **Day 9 — Distribution: Directory Blitz**\n   - Submit product to 15+ relevant directories\n   - Craft directory-specific hooks using interview data\n   - *Skill*: `channel-playbook` (directory-blitz template)\n   - *Output*: Directory submission tracker\n\n   **Day 10 — Community: Engagement Strike**\n   - Join 3-5 Slack\u002FDiscord communities where ICP hangs out\n   - Share one fresh insight chart from interview data\n   - Offer free office-hours or AMA slot\n   - **Decision Gate 2**: Check wait-list size against threshold\n   - *Skill*: `channel-playbook` (community tactics)\n   - *Output*: Community post drafts\n\n   **Day 11 — Competitor: Poaching Play**\n   - Identify 50-100 competitor reviewers (G2, Capterra, Reddit)\n   - Send value-first outreach: \"What's frustrating about [competitor]?\"\n   - Offer concierge migration or white-glove onboarding\n   - *Skill*: `channel-playbook` (competitor-poaching template)\n   - *Output*: Competitor outreach templates\n\n   **Day 12 — Demo Day: Show & Tell**\n   - Live demo to LOI signers and top prospects\n   - Capture video testimonials (even 30-second clips)\n   - Post build-in-public recap with traction metrics\n   - *Output*: Demo script, testimonial clips, recap post draft\n\n   **Day 13 — Sprint Retrospective**\n   - Review all metrics vs. targets\n   - Decide top 3 growth experiments for next 30 days\n   - Publish internal retro + public \"what's next\" post\n   - *Skill*: `retrospective` (or standalone retro)\n   - *Output*: GTM Sprint Report artifact\n\n   #### Sprint Duration Variants\n\n   **7-Day Sprint** (compressed):\n   - Days 0-1: ICP + Interviews (combine Prep + Pain Discovery)\n   - Day 2: Synthesize + Refine MVP\n   - Day 3: LOIs + Positioning\n   - Day 4: Landing Page + Lead Magnet\n   - Day 5: Distribution Blitz + Community\n   - Day 6: Demo Day + Retrospective\n   - Gate Check: Day 3 (mid-sprint)\n\n   **21-Day Sprint** (extended):\n   - Week 1: Days 0-6 (same as 14-day)\n   - Week 2: Days 7-13 (same as 14-day)\n   - Week 3: Days 14-20 — Optimize & Scale\n     - Day 14-15: A\u002FB test landing page variants\n     - Day 16-17: Double down on best-performing channel\n     - Day 18: Pitch deck assembly\n     - Day 19: Investor\u002Fpartner outreach\n     - Day 20: Sprint close + 30-day plan\n   - Gate Check: Day 6, Day 13, Day 18\n\n5. **Adapt for Existing Progress**\n\n   Skip steps where artifacts already exist:\n   - ICP artifact exists and is approved -> skip Day 0 ICP work\n   - 10+ CONV- artifacts exist -> reduce Day 1-2 interview targets\n   - Positioning artifact exists -> skip Day 5 positioning (just do build-in-public)\n   - Landing page copy exists -> skip Day 7 copy work (focus on deployment)\n\n### Phase 2: Decision Gates\n\n6. **Define Quantified Gates**\n\n   Each gate has a metric, threshold, and corrective action:\n\n   | Gate | Day | Metric | Threshold | If Below |\n   |------|-----|--------|-----------|----------|\n   | Interview Volume | 2 | Completed interviews | >= 15 (of 20 target) | Extend Days 1-2 by 1-2 days, increase outreach volume |\n   | Pain Clarity | 3 | Distinct pain themes with $$ quantification | >= 3 themes | Broaden interview scope to adjacent ICP segments |\n   | LOI Commitment | 6 | Signed\u002Fverbal LOIs | >= 60% of target | Double interview volume in Week 2, revisit ICP criteria |\n   | Wait-list Traction | 10 | Wait-list sign-ups | >= 50% of target | Rerun positioning, test different channels, check landing page conversion |\n   | Distribution Reach | 12 | Directory submissions + community posts | >= 10 combined | Focus remaining days on single highest-ROI channel |\n\n   **Gate Severity by Stage:**\n   - `idea`: All gates are advisory (warnings) — learning is the goal\n   - `mvp`: LOI and Wait-list gates are enforced — market signal is critical\n   - `growth`\u002F`scale`: All gates enforced — must hit thresholds to continue\n\n7. **Gate Check Procedure** (Mode: `gate-check`)\n\n   When a gate is triggered:\n   1. Count the relevant metric from artifacts (CONV- count, LOI count, etc.)\n   2. Compare against threshold\n   3. If PASS: congratulate, move to next phase\n   4. If FAIL: present corrective action with specific steps\n   5. Ask user: \"Adjust the plan, override the gate, or pause the sprint?\"\n\n### Phase 3: Sprint Artifacts\n\n8. **GTM Sprint Plan Artifact**\n\n   Save to `artifacts\u002Fgrowth\u002FGTM-SPRINT-{date}.md`:\n\n   ```yaml\n   ---\n   id: GTM-SPRINT-{date}\n   type: launch-brief\n   title: \"GTM Sprint Plan — {objective}\"\n   status: draft\n   created: {date}\n   author: Growth Agent\n   sprint_duration: 14\n   sprint_start: {date}\n   sprint_end: {date+duration}\n   target_interviews: 20\n   target_lois: 5\n   target_waitlist: 50\n   ---\n   ```\n\n   Body contains the full daily task schedule with checkboxes.\n\n9. **GTM Sprint Report Artifact** (end of sprint)\n\n   Save to `artifacts\u002Fgrowth\u002FGTM-SPRINT-REPORT-{date}.md`:\n\n   ```yaml\n   ---\n   id: GTM-SPRINT-REPORT-{date}\n   type: launch-brief\n   title: \"GTM Sprint Report — {objective}\"\n   status: review\n   created: {sprint_end_date}\n   author: Growth Agent\n   parent: GTM-SPRINT-{date}\n   ---\n   ```\n\n   Body contains:\n   - **Metrics vs. Targets**: interviews, LOIs, wait-list, directory submissions, community engagement\n   - **Top Learnings**: 3-5 key insights from interviews\n   - **Pain Matrix Summary**: top 3 validated pain points with $$ impact\n   - **Positioning Validation**: what resonated, what didn't\n   - **Channel Performance**: which channels drove most traction\n   - **Next 30 Days**: top 3 growth experiments recommended\n   - **Decision**: proceed to `\u002Fship`, pivot positioning, expand ICP, or pause\n\n### Phase 4: Status Tracking (Mode: `status`)\n\n10. **Progress Dashboard**\n\n    When invoked with `status`:\n    1. Find the most recent GTM-SPRINT- artifact in `artifacts\u002Fgrowth\u002F`\n    2. Calculate current sprint day based on `sprint_start` date\n    3. Count completed metrics:\n       - CONV- artifacts created since sprint start\n       - LOI artifacts in `artifacts\u002Fproduct\u002F`\n       - Landing page \u002F positioning artifacts created\n       - Channel playbook artifacts created\n    4. Present progress:\n\n    ```\n    ## GTM Sprint Status — Day {N} of {duration}\n\n    ### Metrics\n    | Metric | Target | Current | Status |\n    |--------|--------|---------|--------|\n    | Interviews | 20 | 12 | On track |\n    | LOIs | 5 | 2 | At risk |\n    | Wait-list | 50 | 8 | Behind |\n\n    ### Today's Focus\n    - [Day N tasks from the plan]\n\n    ### Upcoming Gate\n    - Gate: LOI Commitment (Day 6) — need 3 more LOIs in 2 days\n    ```\n\n## LOI (Letter of Intent) Template\n\nWhen creating LOI artifacts on Day 4, save to `artifacts\u002Fproduct\u002FLOI-{company}-{date}.md` using this structure:\n\n```yaml\n---\nid: LOI-{company}-{date}\ntype: loi\ntitle: \"Letter of Intent — {Company Name}\"\nstatus: draft\ncreated: {date}\nauthor: {user}\nparent: {icp-artifact-id}\n---\n```\n\n### LOI Body Template\n\n```markdown\n## Letter of Intent\n\n**From**: {Prospect Name}, {Role} at {Company}\n**To**: {Your Company}\n**Date**: {date}\n\n### Problem Acknowledged\n{1-2 sentences describing the pain point this prospect validated}\n\n### Proposed Solution\n{1-2 sentences describing what you plan to build\u002Foffer}\n\n### Commitment Level\n- [ ] Verbal interest\n- [ ] Email confirmation\n- [ ] Signed LOI\n- [ ] Pilot agreement with timeline\n\n### Terms (if applicable)\n- **Pilot Duration**: {e.g., 30 days}\n- **Pilot Scope**: {what they'll use}\n- **Success Criteria**: {what \"working\" looks like for them}\n- **Pricing Discussion**: {willingness-to-pay signal}\n\n### Prospect Context\n- **Company Size**: {employees \u002F revenue range}\n- **Current Workaround**: {how they solve this today}\n- **$$ Impact**: {estimated cost of current pain per month\u002Fyear}\n- **ICP Fit**: Strong \u002F Partial \u002F Weak\n- **Decision Timeline**: {when they need a solution}\n\n### Next Steps\n{Agreed follow-up actions}\n```\n\n## Cross-References\n\n- **icp-positioning** (S-PROD-01) — Day 0 ICP definition\n- **customer-conversations** (S-PROD-08) — Days 1-2 interview prep\u002Fdebrief, Mom-Test mode\n- **feedback-synthesizer** (S-PROD-04) — Day 2 pain synthesis with Pain Matrix\n- **prd-writer** (S-PROD-02) — Day 3 MVP refinement\n- **positioning-messaging** (S-GRO-01) — Day 5 narrative and positioning\n- **landing-page-copy** (S-GRO-02) — Day 7 launch page\n- **content-engine** (S-GRO-07) — Day 8 lead magnet\n- **channel-playbook** (S-GRO-04) — Days 9-11 distribution (directory blitz, community, competitor poaching)\n- **retrospective** (S-ORG-14) — Day 13 sprint retro\n- **ship** (S-ORG-08) — post-sprint graduation to full build flow\n\n## Quality Checklist\n- [ ] Sprint duration is appropriate for company stage\n- [ ] Daily tasks are specific and actionable\n- [ ] Decision gates have quantified thresholds\n- [ ] Existing artifacts are accounted for (no duplicate work)\n- [ ] Skill sequencing follows dependency order\n- [ ] LOI template is included for Day 4\n- [ ] Sprint plan adapts to 7\u002F14\u002F21 day variants\n- [ ] Sprint report captures metrics vs. targets\n- [ ] Corrective actions are specific for each failed gate\n- [ ] Artifact passes validation\n","# GTM Sprint\n\n## When to Use\n\n- Pre-product validation: \"Do people actually want this?\"\n- MVP launch: \"We built it, now how do we get users?\"\n- New market entry: \"We're expanding to a new segment\"\n- Repositioning: \"Our current positioning isn't working\"\n- Any time the user says: \"go to market\", \"GTM\", \"launch plan\", \"validate market\", \"find customers\"\n\n## Reference\n- **ID**: S-GRO-09\n- **Category**: Growth\n- **Inputs**: company.config.yaml, ICP artifact (or triggers creation), objective description\n- **Outputs**: GTM Sprint Plan artifact + GTM Sprint Report artifact -> artifacts\u002Fgrowth\u002F\n- **Used by**: Growth Agent\n- **Tool scripts**: .\u002Ftools\u002Fartifact\u002Fvalidate.sh\n\n## Purpose\n\nOrchestrates a time-boxed go-to-market sprint that sequences validation, commitment, launch, and distribution into a structured daily cadence with quantified decision gates. Unlike `\u002Fship` (which builds software) or `\u002Frapid-prototype` (which proves technical feasibility), `\u002Fgtm-sprint` validates **market demand** and builds **distribution** — no code required.\n\nInspired by the 100x GTM Playbook methodology: validate with interviews, secure commitments (LOIs), build launch assets, activate distribution channels, and measure traction — all within a fixed sprint window.\n\n## When NOT to Use\n\n- Building software features -> use `\u002Fship`\n- Technical proof-of-concept -> use `\u002Frapid-prototype`\n- Single-channel optimization -> use `\u002Fchannel-playbook` directly\n- Post-launch growth optimization -> use individual growth skills directly\n\n## What You Will See\n\n`\u002Fgtm-sprint plan 14` produces a plan like this (excerpt). Each day lists tasks, the skill to use and the output.\n\n```text\nGTM Sprint Plan: Acme Invoices, 14 days, stage: idea\n\nDay 0  Prep: lock ICP and outreach\n  - Finalize ICP (role, company size, budget, current workaround)\n  - Build a 100-name prospect list; book 15+ calls for Days 1-2\n  - Skill: icp-positioning        Output: ICP artifact, prospect list\nDay 1  Pain discovery: Mom-Test interviews (10+, 15 min each)\n  - Skill: customer-conversations prep mom-test\n  - Output: 10+ CONV- artifacts\nDay 2  Insights: synthesize pain data\n  - Skill: feedback-synthesizer   Output: Pain Matrix\n  Gate: Interview Volume (>= 15 completed)\n```\n\n`\u002Fgtm-sprint gate-check` evaluates one gate and tells you what to do next:\n\n```text\nGate: Interview Volume (Day 2)   Metric: completed interviews\nThreshold: >= 15   Actual: 11   Result: FAIL (advisory at stage idea)\nCorrective action: extend Days 1-2 by 1-2 days and increase outreach volume.\nAdjust the plan, override the gate, or pause the sprint?\n```\n\nAnswer with `adjust`, `override` or `pause`. Gates are advisory at `idea` stage and enforced at `growth` and `scale`.\n\n## Modes\n\n### Mode: `plan` (default)\n\nGenerates a personalized GTM Sprint Plan with daily tasks, decision gates, and skill sequencing.\n\n### Mode: `status`\n\nReviews progress against the active GTM Sprint Plan — checks completed tasks, gate metrics, and recommends adjustments.\n\n### Mode: `gate-check`\n\nEvaluates a specific decision gate and recommends corrective action if thresholds are not met.\n\n## Procedure\n\n### Phase 0: Context & Configuration\n\n1. **Load Context**\n   - Read `company.config.yaml` for company name, stage, product description\n   - Check `artifacts\u002Fproduct\u002F` for existing ICP artifact\n   - Check `artifacts\u002Fdecision-memos\u002F` for existing CONV- artifacts (interview count)\n   - Check `artifacts\u002Fgrowth\u002F` for existing positioning, landing page, channel playbooks\n\n2. **Sprint Configuration**\n\n   Ask the user for (with smart defaults):\n\n   | Parameter | Default | Options |\n   |-----------|---------|---------|\n   | Sprint duration | 14 days | 7 \u002F 14 \u002F 21 days |\n   | Start date | Today | Any date |\n   | Objective | From product description | Custom |\n   | Target LOIs | 5 | 3-10 |\n   | Target interviews | 20 | 10-30 |\n   | Target wait-list | 50 | 25-200 |\n\n   Stage-aware defaults:\n   - `idea`: 14 days, 20 interviews, 5 LOIs, 50 wait-list\n   - `mvp`: 7 days (validation done), 10 interviews, 3 LOIs, 100 wait-list\n   - `growth`: 7 days (repositioning sprint), 15 interviews, 5 LOIs, 200 wait-list\n\n3. **ICP Check**\n   - If no ICP artifact exists: inform the user — \"No ICP found. The sprint will begin with ICP definition (Day 0). Run `\u002Ficp-positioning` now, or we'll include it in the sprint plan.\"\n   - If ICP exists but is `draft`: note it needs validation through interviews\n\n### Phase 1: Generate Sprint Plan (Mode: `plan`)\n\n4. **Build Daily Task Schedule**\n\n   Generate a day-by-day plan adapted to the sprint duration. For a 14-day sprint:\n\n   #### Week 1: Validate & Commit (Days 0-6)\n\n   **Day 0 — Prep: Lock ICP & Outreach**\n   - Finalize ICP criteria (role, company size, budget, current workaround)\n   - Build prospect list (100 targets) — use LinkedIn, communities, competitor reviews\n   - Book 15+ discovery calls for Days 1-2\n   - *Skill*: `icp-positioning` (if no ICP exists)\n   - *Skill*: `customer-conversations prep cold-outreach`\n   - *Output*: ICP artifact (draft or updated), prospect list\n\n   **Day 1 — Pain Discovery: Mom-Test Interviews**\n   - Conduct 10+ Mom-Test interviews (15 min each)\n   - Record key quotes and $$ impact of each pain point\n   - Focus: current behavior, cost of status quo, workarounds tried\n   - *Skill*: `customer-conversations prep mom-test`\n   - *Skill*: `customer-conversations debrief` (after each call)\n   - *Output*: 10+ CONV- artifacts\n\n   **Day 2 — Insights: Synthesize Pain Data**\n   - Conduct remaining interviews (target: 20 total)\n   - Run feedback synthesis on all CONV- artifacts\n   - Produce Pain Matrix: themes clustered by $$ impact + urgency\n   - Rank themes, identify top 3 \"hair-on-fire\" problems\n   - *Skill*: `feedback-synthesizer` (with pain-matrix output)\n   - *Output*: Feedback report with Pain Matrix\n\n   **Day 3 — Refine: Sharpen MVP Scope**\n   - Map current workflow -> desired workflow for top pain\n   - Update MVP scope based on Day 2 insights\n   - Quantify time saved and cost saved per user\n   - Draft value proposition: \"We help X do Y, saving Z hours\u002Fweek\"\n   - *Skill*: `prd-writer` or update existing PRD\n   - *Output*: Updated PRD or mini-PRD (if pre-product)\n\n   **Day 4 — Commit: Secure Letters of Intent**\n   - Draft 1-page LOI template (problem, proposed solution, commitment level, timeline)\n   - Re-contact top 5 prospects from interviews\n   - Show prototype\u002Fmockup\u002Fdemo and request commitment\n   - Obtain verbal commitments or e-signatures\n   - *Output*: LOI artifacts (target: 5 signed)\n\n   **Day 5 — Narrative: Go Public**\n   - Write 1-sentence mission statement\n   - Write 2-paragraph vision statement\n   - Craft positioning: \"We help [X] do [Y] in [Z] seconds\"\n   - Publish first build-in-public post\n   - *Skill*: `positioning-messaging`\n   - *Skill*: `channel-playbook` (build-in-public arc)\n   - *Output*: Positioning artifact, first public post draft\n\n   **Day 6 — Gate Check: Week 1 Review**\n   - Review metrics: interviews completed, LOIs signed, wait-list size\n   - **Decision Gate 1**: Evaluate against thresholds (see Decision Gates below)\n   - Adjust Week 2 plan based on gate results\n   - *Output*: Week 1 status update\n\n   #### Week 2: Launch & Grow (Days 7-13)\n\n   **Day 7 — Launch Pad: Landing Page**\n   - Build landing page with top 3 pain quotes above the fold\n   - Embed email capture \u002F wait-list form\n   - Add Calendly or booking link for demos\n   - *Skill*: `landing-page-copy`\n   - *Output*: Landing page copy artifact (or deployed page)\n\n   **Day 8 — Lead Magnet: Field Report**\n   - Compile interview insights into a downloadable asset\n   - Format: \"Field Report\" PDF, industry brief, or data snapshot\n   - Gate the download behind email capture\n   - *Skill*: `content-engine` (lead-magnet format)\n   - *Output*: Lead magnet content artifact\n\n   **Day 9 — Distribution: Directory Blitz**\n   - Submit product to 15+ relevant directories\n   - Craft directory-specific hooks using interview data\n   - *Skill*: `channel-playbook` (directory-blitz template)\n   - *Output*: Directory submission tracker\n\n   **Day 10 — Community: Engagement Strike**\n   - Join 3-5 Slack\u002FDiscord communities where ICP hangs out\n   - Share one fresh insight chart from interview data\n   - Offer free office-hours or AMA slot\n   - **Decision Gate 2**: Check wait-list size against threshold\n   - *Skill*: `channel-playbook` (community tactics)\n   - *Output*: Community post drafts\n\n   **Day 11 — Competitor: Poaching Play**\n   - Identify 50-100 competitor reviewers (G2, Capterra, Reddit)\n   - Send value-first outreach: \"What's frustrating about [competitor]?\"\n   - Offer concierge migration or white-glove onboarding\n   - *Skill*: `channel-playbook` (competitor-poaching template)\n   - *Output*: Competitor outreach templates\n\n   **Day 12 — Demo Day: Show & Tell**\n   - Live demo to LOI signers and top prospects\n   - Capture video testimonials (even 30-second clips)\n   - Post build-in-public recap with traction metrics\n   - *Output*: Demo script, testimonial clips, recap post draft\n\n   **Day 13 — Sprint Retrospective**\n   - Review all metrics vs. targets\n   - Decide top 3 growth experiments for next 30 days\n   - Publish internal retro + public \"what's next\" post\n   - *Skill*: `retrospective` (or standalone retro)\n   - *Output*: GTM Sprint Report artifact\n\n   #### Sprint Duration Variants\n\n   **7-Day Sprint** (compressed):\n   - Days 0-1: ICP + Interviews (combine Prep + Pain Discovery)\n   - Day 2: Synthesize + Refine MVP\n   - Day 3: LOIs + Positioning\n   - Day 4: Landing Page + Lead Magnet\n   - Day 5: Distribution Blitz + Community\n   - Day 6: Demo Day + Retrospective\n   - Gate Check: Day 3 (mid-sprint)\n\n   **21-Day Sprint** (extended):\n   - Week 1: Days 0-6 (same as 14-day)\n   - Week 2: Days 7-13 (same as 14-day)\n   - Week 3: Days 14-20 — Optimize & Scale\n     - Day 14-15: A\u002FB test landing page variants\n     - Day 16-17: Double down on best-performing channel\n     - Day 18: Pitch deck assembly\n     - Day 19: Investor\u002Fpartner outreach\n     - Day 20: Sprint close + 30-day plan\n   - Gate Check: Day 6, Day 13, Day 18\n\n5. **Adapt for Existing Progress**\n\n   Skip steps where artifacts already exist:\n   - ICP artifact exists and is approved -> skip Day 0 ICP work\n   - 10+ CONV- artifacts exist -> reduce Day 1-2 interview targets\n   - Positioning artifact exists -> skip Day 5 positioning (just do build-in-public)\n   - Landing page copy exists -> skip Day 7 copy work (focus on deployment)\n\n### Phase 2: Decision Gates\n\n6. **Define Quantified Gates**\n\n   Each gate has a metric, threshold, and corrective action:\n\n   | Gate | Day | Metric | Threshold | If Below |\n   |------|-----|--------|-----------|----------|\n   | Interview Volume | 2 | Completed interviews | >= 15 (of 20 target) | Extend Days 1-2 by 1-2 days, increase outreach volume |\n   | Pain Clarity | 3 | Distinct pain themes with $$ quantification | >= 3 themes | Broaden interview scope to adjacent ICP segments |\n   | LOI Commitment | 6 | Signed\u002Fverbal LOIs | >= 60% of target | Double interview volume in Week 2, revisit ICP criteria |\n   | Wait-list Traction | 10 | Wait-list sign-ups | >= 50% of target | Rerun positioning, test different channels, check landing page conversion |\n   | Distribution Reach | 12 | Directory submissions + community posts | >= 10 combined | Focus remaining days on single highest-ROI channel |\n\n   **Gate Severity by Stage:**\n   - `idea`: All gates are advisory (warnings) — learning is the goal\n   - `mvp`: LOI and Wait-list gates are enforced — market signal is critical\n   - `growth`\u002F`scale`: All gates enforced — must hit thresholds to continue\n\n7. **Gate Check Procedure** (Mode: `gate-check`)\n\n   When a gate is triggered:\n   1. Count the relevant metric from artifacts (CONV- count, LOI count, etc.)\n   2. Compare against threshold\n   3. If PASS: congratulate, move to next phase\n   4. If FAIL: present corrective action with specific steps\n   5. Ask user: \"Adjust the plan, override the gate, or pause the sprint?\"\n\n### Phase 3: Sprint Artifacts\n\n8. **GTM Sprint Plan Artifact**\n\n   Save to `artifacts\u002Fgrowth\u002FGTM-SPRINT-{date}.md`:\n\n   ```yaml\n   ---\n   id: GTM-SPRINT-{date}\n   type: launch-brief\n   title: \"GTM Sprint Plan — {objective}\"\n   status: draft\n   created: {date}\n   author: Growth Agent\n   sprint_duration: 14\n   sprint_start: {date}\n   sprint_end: {date+duration}\n   target_interviews: 20\n   target_lois: 5\n   target_waitlist: 50\n   ---\n   ```\n\n   Body contains the full daily task schedule with checkboxes.\n\n9. **GTM Sprint Report Artifact** (end of sprint)\n\n   Save to `artifacts\u002Fgrowth\u002FGTM-SPRINT-REPORT-{date}.md`:\n\n   ```yaml\n   ---\n   id: GTM-SPRINT-REPORT-{date}\n   type: launch-brief\n   title: \"GTM Sprint Report — {objective}\"\n   status: review\n   created: {sprint_end_date}\n   author: Growth Agent\n   parent: GTM-SPRINT-{date}\n   ---\n   ```\n\n   Body contains:\n   - **Metrics vs. Targets**: interviews, LOIs, wait-list, directory submissions, community engagement\n   - **Top Learnings**: 3-5 key insights from interviews\n   - **Pain Matrix Summary**: top 3 validated pain points with $$ impact\n   - **Positioning Validation**: what resonated, what didn't\n   - **Channel Performance**: which channels drove most traction\n   - **Next 30 Days**: top 3 growth experiments recommended\n   - **Decision**: proceed to `\u002Fship`, pivot positioning, expand ICP, or pause\n\n### Phase 4: Status Tracking (Mode: `status`)\n\n10. **Progress Dashboard**\n\n    When invoked with `status`:\n    1. Find the most recent GTM-SPRINT- artifact in `artifacts\u002Fgrowth\u002F`\n    2. Calculate current sprint day based on `sprint_start` date\n    3. Count completed metrics:\n       - CONV- artifacts created since sprint start\n       - LOI artifacts in `artifacts\u002Fproduct\u002F`\n       - Landing page \u002F positioning artifacts created\n       - Channel playbook artifacts created\n    4. Present progress:\n\n    ```\n    ## GTM Sprint Status — Day {N} of {duration}\n\n    ### Metrics\n    | Metric | Target | Current | Status |\n    |--------|--------|---------|--------|\n    | Interviews | 20 | 12 | On track |\n    | LOIs | 5 | 2 | At risk |\n    | Wait-list | 50 | 8 | Behind |\n\n    ### Today's Focus\n    - [Day N tasks from the plan]\n\n    ### Upcoming Gate\n    - Gate: LOI Commitment (Day 6) — need 3 more LOIs in 2 days\n    ```\n\n## LOI (Letter of Intent) Template\n\nWhen creating LOI artifacts on Day 4, save to `artifacts\u002Fproduct\u002FLOI-{company}-{date}.md` using this structure:\n\n```yaml\n---\nid: LOI-{company}-{date}\ntype: loi\ntitle: \"Letter of Intent — {Company Name}\"\nstatus: draft\ncreated: {date}\nauthor: {user}\nparent: {icp-artifact-id}\n---\n```\n\n### LOI Body Template\n\n```markdown\n## Letter of Intent\n\n**From**: {Prospect Name}, {Role} at {Company}\n**To**: {Your Company}\n**Date**: {date}\n\n### Problem Acknowledged\n{1-2 sentences describing the pain point this prospect validated}\n\n### Proposed Solution\n{1-2 sentences describing what you plan to build\u002Foffer}\n\n### Commitment Level\n- [ ] Verbal interest\n- [ ] Email confirmation\n- [ ] Signed LOI\n- [ ] Pilot agreement with timeline\n\n### Terms (if applicable)\n- **Pilot Duration**: {e.g., 30 days}\n- **Pilot Scope**: {what they'll use}\n- **Success Criteria**: {what \"working\" looks like for them}\n- **Pricing Discussion**: {willingness-to-pay signal}\n\n### Prospect Context\n- **Company Size**: {employees \u002F revenue range}\n- **Current Workaround**: {how they solve this today}\n- **$$ Impact**: {estimated cost of current pain per month\u002Fyear}\n- **ICP Fit**: Strong \u002F Partial \u002F Weak\n- **Decision Timeline**: {when they need a solution}\n\n### Next Steps\n{Agreed follow-up actions}\n```\n\n## Cross-References\n\n- **icp-positioning** (S-PROD-01) — Day 0 ICP definition\n- **customer-conversations** (S-PROD-08) — Days 1-2 interview prep\u002Fdebrief, Mom-Test mode\n- **feedback-synthesizer** (S-PROD-04) — Day 2 pain synthesis with Pain Matrix\n- **prd-writer** (S-PROD-02) — Day 3 MVP refinement\n- **positioning-messaging** (S-GRO-01) — Day 5 narrative and positioning\n- **landing-page-copy** (S-GRO-02) — Day 7 launch page\n- **content-engine** (S-GRO-07) — Day 8 lead magnet\n- **channel-playbook** (S-GRO-04) — Days 9-11 distribution (directory blitz, community, competitor poaching)\n- **retrospective** (S-ORG-14) — Day 13 sprint retro\n- **ship** (S-ORG-08) — post-sprint graduation to full build flow\n\n## Quality Checklist\n- [ ] Sprint duration is appropriate for company stage\n- [ ] Daily tasks are specific and actionable\n- [ ] Decision gates have quantified thresholds\n- [ ] Existing artifacts are accounted for (no duplicate work)\n- [ ] Skill sequencing follows dependency order\n- [ ] LOI template is included for Day 4\n- [ ] Sprint plan adapts to 7\u002F14\u002F21 day variants\n- [ ] Sprint report captures metrics vs. targets\n- [ ] Corrective actions are specific for each failed gate\n- [ ] Artifact passes validation\n",{"name":5,"description":7,"argument-hint":38,"user-invocable":39},"[plan | status | gate-check] [7 | 14 | 21]",true,"main","e842fb6d0e04360c47db78bc2e2e2987314d64d4",".claude\u002Fskills\u002Fgtm-sprint",2,"https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os","https:\u002F\u002Fgithub.com\u002Fvibbs","Principal Engineer · Applied AI · building ArcAI @ GrowthArc","2026-10-21 02:08:08",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":39},[50,53,56],{"tool":51,"command":52},"npx","npx skills add vibbs\u002Fcompany-os --skill gtm-sprint",{"tool":54,"command":55},"bunx","bunx skills add vibbs\u002Fcompany-os --skill gtm-sprint",{"tool":57,"command":58},"pnpm","pnpm dlx skills add vibbs\u002Fcompany-os --skill gtm-sprint","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgtm-sprint\u002FSKILL.md",[],[62,71,79,89,105,123],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":33},"01M6CTHBW1E64ECYGD105N4S5E","typo-field","Fixture skill with a misspelled top-level field.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Ftypo-field\u002FSKILL.md",[],[69,70],"typo field","fixture skill",{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":33},"01M6CTHABTV8FKVDHFMMKPAV51","spaced-comments","Fixture skill with comments and spaces after block keys.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fspaced-comments\u002FSKILL.md",[],[78,70],"spaced comments",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":33},"01M6CTH8MHC14KB65ZDHYBJW1N","crlf-comments","Fixture skill with Windows line endings.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fcrlf-comments\u002FSKILL.md",[],[86,87,88,70],"crlf comments","CRLF","windows",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":33},"01M6CTH6TBKTDP9G8QB1Z2K0TY","claude-fields","Fixture skill using top-level fields Claude Code documents.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fclaude-fields\u002FSKILL.md",[],[96,97,98,99,100,101,70,102,103,104],"claude fields","explore","documents","src","grep","read","Bash","code","testing",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":116,"publishedAt":33},"01M6CTH46BGKXH80RWS876Y2CW","workflow-router","Maps an objective to the artifacts, stages and agents it needs. Use when deciding what happens next or which agents to involve.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fworkflow-router\u002FSKILL.md",[111],{"categoryNo":112,"categoryName":113,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[117,118,119,120,121,29,122],"workflow","router","workflow router","next","maps","artifacts",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":33},"01M6CTH27653SRVP2FMEQN3J5B","weekly-review","Summarizes your week: what shipped, AI spend, support themes, security health and next priorities. Use at the end of each week.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[130,131,132,120,29,133,134,135,136],"weekly review","review","priorities","health","save","support","security"]