メニュー
Time-boxed go-to-market sprint that sequences customer validation, positioning, launch, and distribution over 7-21 days. Use when validating market demand, launching an MVP, or running a structured GTM push.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Interactive setup wizard for Company OS. Configures company.config.yaml, generates .claude/settings.json with tech-stack-specific permissions, and scaffolds directories. Supports three modes — interactive wizard, express config block, or auto-extract from a URL/unstructured text.
Produces RFC/ADR defining system boundaries, modules, data model, and integration points. Use when translating a PRD into technical design, making architectural decisions, or designing new system components.
Produces architecture diagrams, data flow diagrams, ERDs, and system overviews in Mermaid (inline) and Excalidraw JSON (standalone). Use when an RFC, threat model, or documentation needs visual diagrams.
Performs data flow threat analysis with structured mitigations. Use when assessing security threats for new features, architecture changes, or compliance reviews.
Creates platform-specific marketing playbooks for acquisition channels. Use when launching or optimizing a specific growth channel (e.g., LinkedIn, Twitter, email, Product Hunt).
Prepares pre-call briefings, captures post-call debriefs, and routes insights to ICP refinement and PRD evidence. Stores conversation logs as CONV- artifacts in artifacts/decision-memos/.
| name | gtm-sprint |
| description | Time-boxed go-to-market sprint that sequences customer validation, positioning, launch, and distribution over 7-21 days. Use when validating market demand, launching an MVP, or running a structured GTM push. |
| user-invokable | true |
| argument-hint | plan | status | gate-check |
Orchestrates a time-boxed go-to-market sprint that sequences validation, commitment, launch, and distribution into a structured daily cadence with quantified decision gates. Unlike /ship (which builds software) or /prototype (which proves technical feasibility), /gtm-sprint validates market demand and builds distribution — no code required.
Inspired 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.
/ship/prototype/channel-playbook directlyplan (default)Generates a personalized GTM Sprint Plan with daily tasks, decision gates, and skill sequencing.
statusReviews progress against the active GTM Sprint Plan — checks completed tasks, gate metrics, and recommends adjustments.
gate-checkEvaluates a specific decision gate and recommends corrective action if thresholds are not met.
Load Context
company.config.yaml for company name, stage, product descriptionartifacts/product/ for existing ICP artifactartifacts/decision-memos/ for existing CONV- artifacts (interview count)artifacts/growth/ for existing positioning, landing page, channel playbooksSprint Configuration
Ask the user for (with smart defaults):
| Parameter | Default | Options |
|---|---|---|
| Sprint duration | 14 days | 7 / 14 / 21 days |
| Start date | Today | Any date |
| Objective | From product description | Custom |
| Target LOIs | 5 | 3-10 |
| Target interviews | 20 | 10-30 |
| Target wait-list | 50 | 25-200 |
Stage-aware defaults:
idea: 14 days, 20 interviews, 5 LOIs, 50 wait-listmvp: 7 days (validation done), 10 interviews, 3 LOIs, 100 wait-listgrowth: 7 days (repositioning sprint), 15 interviews, 5 LOIs, 200 wait-listICP Check
/icp-positioning now, or we'll include it in the sprint plan."draft: note it needs validation through interviewsplan)Build Daily Task Schedule
Generate a day-by-day plan adapted to the sprint duration. For a 14-day sprint:
Day 0 — Prep: Lock ICP & Outreach
icp-positioning (if no ICP exists)customer-conversations prep cold-outreachDay 1 — Pain Discovery: Mom-Test Interviews
customer-conversations prep mom-testcustomer-conversations debrief (after each call)Day 2 — Insights: Synthesize Pain Data
feedback-synthesizer (with pain-matrix output)Day 3 — Refine: Sharpen MVP Scope
prd-writer or update existing PRDDay 4 — Commit: Secure Letters of Intent
Day 5 — Narrative: Go Public
positioning-messagingchannel-playbook (build-in-public arc)Day 6 — Gate Check: Week 1 Review
Day 7 — Launch Pad: Landing Page
landing-page-copyDay 8 — Lead Magnet: Field Report
content-engine (lead-magnet format)Day 9 — Distribution: Directory Blitz
channel-playbook (directory-blitz template)Day 10 — Community: Engagement Strike
channel-playbook (community tactics)Day 11 — Competitor: Poaching Play
channel-playbook (competitor-poaching template)Day 12 — Demo Day: Show & Tell
Day 13 — Sprint Retrospective
retrospective (or standalone retro)7-Day Sprint (compressed):
21-Day Sprint (extended):
Adapt for Existing Progress
Skip steps where artifacts already exist:
Define Quantified Gates
Each gate has a metric, threshold, and corrective action:
| Gate | Day | Metric | Threshold | If Below |
|---|---|---|---|---|
| Interview Volume | 2 | Completed interviews | >= 15 (of 20 target) | Extend Days 1-2 by 1-2 days, increase outreach volume |
| Pain Clarity | 3 | Distinct pain themes with $$ quantification | >= 3 themes | Broaden interview scope to adjacent ICP segments |
| LOI Commitment | 6 | Signed/verbal LOIs | >= 60% of target | Double interview volume in Week 2, revisit ICP criteria |
| Wait-list Traction | 10 | Wait-list sign-ups | >= 50% of target | Rerun positioning, test different channels, check landing page conversion |
| Distribution Reach | 12 | Directory submissions + community posts | >= 10 combined | Focus remaining days on single highest-ROI channel |
Gate Severity by Stage:
idea: All gates are advisory (warnings) — learning is the goalmvp: LOI and Wait-list gates are enforced — market signal is criticalgrowth/scale: All gates enforced — must hit thresholds to continueGate Check Procedure (Mode: gate-check)
When a gate is triggered:
GTM Sprint Plan Artifact
Save to artifacts/growth/GTM-SPRINT-{date}.md:
---
id: GTM-SPRINT-{date}
type: launch-brief
title: "GTM Sprint Plan — {objective}"
status: draft
created: {date}
author: Growth Agent
sprint_duration: 14
sprint_start: {date}
sprint_end: {date+duration}
target_interviews: 20
target_lois: 5
target_waitlist: 50
---
Body contains the full daily task schedule with checkboxes.
GTM Sprint Report Artifact (end of sprint)
Save to artifacts/growth/GTM-SPRINT-REPORT-{date}.md:
---
id: GTM-SPRINT-REPORT-{date}
type: launch-brief
title: "GTM Sprint Report — {objective}"
status: review
created: {sprint_end_date}
author: Growth Agent
parent: GTM-SPRINT-{date}
---
Body contains:
/ship, pivot positioning, expand ICP, or pausestatus)Progress Dashboard
When invoked with status:
artifacts/growth/sprint_start dateartifacts/product/## GTM Sprint Status — Day {N} of {duration}
### Metrics
| Metric | Target | Current | Status |
|--------|--------|---------|--------|
| Interviews | 20 | 12 | On track |
| LOIs | 5 | 2 | At risk |
| Wait-list | 50 | 8 | Behind |
### Today's Focus
- [Day N tasks from the plan]
### Upcoming Gate
- Gate: LOI Commitment (Day 6) — need 3 more LOIs in 2 days
When creating LOI artifacts on Day 4, save to artifacts/product/LOI-{company}-{date}.md using this structure:
---
id: LOI-{company}-{date}
type: loi
title: "Letter of Intent — {Company Name}"
status: draft
created: {date}
author: {user}
parent: {icp-artifact-id}
---
## Letter of Intent
**From**: {Prospect Name}, {Role} at {Company}
**To**: {Your Company}
**Date**: {date}
### Problem Acknowledged
{1-2 sentences describing the pain point this prospect validated}
### Proposed Solution
{1-2 sentences describing what you plan to build/offer}
### Commitment Level
- [ ] Verbal interest
- [ ] Email confirmation
- [ ] Signed LOI
- [ ] Pilot agreement with timeline
### Terms (if applicable)
- **Pilot Duration**: {e.g., 30 days}
- **Pilot Scope**: {what they'll use}
- **Success Criteria**: {what "working" looks like for them}
- **Pricing Discussion**: {willingness-to-pay signal}
### Prospect Context
- **Company Size**: {employees / revenue range}
- **Current Workaround**: {how they solve this today}
- **$$ Impact**: {estimated cost of current pain per month/year}
- **ICP Fit**: Strong / Partial / Weak
- **Decision Timeline**: {when they need a solution}
### Next Steps
{Agreed follow-up actions}