本文へ移動
cccskills
無料GitHub で公開

prd-v09-gtm-strategy

Orchestrate go-to-market strategy by running positioning, offer construction, and channel allocation as a sequenced workflow during PRD v0.9 Go-to-Market. Triggers on requests to plan launch, define GTM strategy, or when user asks "how do we launch?", "go-to-market", "launch plan", "marketing strategy", "GTM", "launch this product". Chains three framework-grounded sub-skills (Dunford → Hormozi → ORB) and reconciles their outputs.

インストール方法を見る

含まれるファイル(6)

  • SKILL.md6.8 KB
  • assets/gtm-template.md14.2 KB
  • references/channel-selection.md13.8 KB
  • references/examples.md12.5 KB
  • references/launch-strategies.md16.0 KB
  • references/messaging-frameworks.md12.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

GTM Strategy (Orchestrator)

Position in workflow: v0.8 Monitoring Setup → v0.9 GTM Strategy (Orchestrator) → v0.9 Launch Metrics

This skill is an orchestrator, not a primary skill. GTM strategy is composed of three framework-grounded sub-skills that run in sequence. This skill chains them and reconciles outputs. New work on positioning, offers, or channels should invoke the sub-skills directly.

Execution Mode

Default is standard. See .claude/rules/08-skill-execution-modes.md for selection logic.

ModeWhat this skill produces
quickEach sub-skill in quick mode; reconciled GTM index
standardEach sub-skill in standard mode; full reconciliation pass over outputs
deepEach sub-skill in deep mode; multi-pass reconciliation + risk register

The Three Sub-Skills

GTM is positioning before offer before channels. Running them out of order produces channel plans that don't reach the right people with the right pitch.

StepSub-skillFrameworkOwner
1prd-v09-positioning-dunfordApril Dunford, Obviously Awesome (5-step)Founder + PM
2prd-v09-offer-construction-hormoziAlex Hormozi, $100M Offers (value equation + Grand Slam)Founder + Sales
3prd-v09-launch-channels-orbCorey Haines, ORB framework (Owned / Rented / Borrowed)Growth

Use the v0.9 tactical playbooks (prd-v09-aeo-audit, prd-v09-alternatives-pages, prd-v09-cold-outreach-tiered, prd-v09-hn-reddit-launch) after these three are complete — each plugs into a specific channel from step 3.

Orchestration Workflow

1. Positioning (Dunford)         →  GTM-*(positioning), BR-POS-*
              ↓
2. Offer (Hormozi)                →  GTM-*(offer, guarantee), BR-PRICING-*
              ↓
3. Channels (ORB)                 →  GTM-*(channel, sequence, mix-matrix)
              ↓
4. Reconciliation (this skill)    →  GTM-*(index) with cross-skill checks
              ↓
5. Tactical playbooks             →  AEO audit, alt pages, cold outreach, HN/Reddit (v0.9 tactical)
              ↓
6. Launch Metrics + Feedback      →  v0.9 Launch Metrics, Feedback Loop Setup

Reconciliation (this skill's actual work)

After the three sub-skills run, check for cross-skill consistency:

CheckQuestionFix if no
Best-fit alignmentAre channels (step 3) actually used by the best-fit segment defined in positioning (step 1)?Re-run step 3 with corrected segment lens
Promise consistencyDoes the offer (step 2) promise more or less than the positioning supports?Adjust offer down; do not silently inflate positioning
Guarantee viabilityCan the guarantee in the offer survive the launch volume from step 3?Tighten guarantee terms or reduce paid-channel reach until guarantee can scale
Category-channel fitIs the launch channel mix appropriate for the market category claimed in positioning?Drop channels that don't fit the category (e.g., enterprise category → no TikTok)
KPI rollupDo per-channel attribution targets sum to v0.3 baseline KPI- targets?Adjust channel budget/effort allocation

Reconciliation is the load-bearing work — without it, the three sub-skill outputs are incoherent.

Consumes

This skill's Consumes is the union of the three sub-skills' Consumes:

  • From v0.2 (CFD-, BR-product-type), v0.3 (FEA-, KPI-, BR-pricing), v0.4 (PER-), v0.8 (DEP-, MON-)
  • See each sub-skill for the specific IDs it pulls

Produces

This skill produces the reconciled GTM- index — a single entry pointing at all GTM- entries created by the three sub-skills, with reconciliation notes:

GTM-XXX: GTM Strategy Index
Type: Index
Owner: Launch Coordinator
Status: Approved

Positioning: GTM-AAA (statement), BR-POS-* (rules)
Offer: GTM-BBB (card), GTM-CCC (guarantee)
Channels: GTM-DDD/EEE/FFF (channel entries), GTM-GGG (mix matrix), GTM-HHH (sequence)
Tactical (when active): GTM-* from AEO, alternatives, cold outreach, HN/Reddit playbooks

Reconciliation notes:
  - Best-fit alignment: [PASS | issue + fix]
  - Promise consistency: [...]
  - Guarantee viability: [...]
  - Category-channel fit: [...]
  - KPI rollup: [...]

Linked IDs: All GTM-* created in this lifecycle iteration

Migration Note (legacy entries)

Prior to this refactor, this skill produced GTM-* entries directly with Type=Messaging, Type=Channel, Type=Timeline, Type=Task, Type=Asset. Existing entries with those types remain valid — the sub-skills produce comparable types structured around their respective frameworks.

If you have legacy GTM-* entries created before the split, run each sub-skill once over the existing material to:

  • Reclassify messaging entries as Type=Positioning (anchored in Dunford's 5 steps)
  • Validate offer-related entries against the Hormozi value equation
  • Reclassify channel entries by ORB layer (Owned / Rented / Borrowed)

No automatic migration — the reclassification is a deliberate decision that surfaces gaps in the original work.

Quality Gates

Before proceeding to Launch Metrics:

  • All three sub-skills have completed (or quick-mode placeholders exist for each)
  • Reconciliation table filled with all five checks (PASS or fix logged)
  • GTM- index entry created pointing at all sub-skill outputs
  • No unreconciled contradictions between positioning, offer, and channels

Downstream Connections

See each sub-skill for direct downstream connections. This orchestrator's downstream is:

ConsumerWhat it uses
v0.9 Tactical playbooksThe GTM index identifies which channels are active for tactical-skill plug-in
v0.9 Launch MetricsThe reconciled KPI rollup
v0.9 Feedback Loop SetupThe reconciled channel list

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Validates gate criteria before PRD lifecycle advancement by delegating to the readiness scoring pipeline (scripts/readiness.py). Returns a graduated PASS / WARN / BLOCK verdict with top blockers and their causal chain. Triggers before advancing from v0.X to v0.Y or explicit `/ghm-gate-check`.

日本語の概要は準備中です。原文の説明を表示しています。

mattgierhart/PRD-driven-context-engineering1812026年8月31日 更新

Extracts durable insights from temp/ files to SoT during EPIC Phase E. Triggers at EPIC completion or explicit `/ghm-harvest` invocation. Outputs new SoT entries and archive manifest.

日本語の概要は準備中です。原文の説明を表示しています。

mattgierhart/PRD-driven-context-engineering1812026年8月31日 更新

Validates and registers new SoT IDs with cross-reference integrity. Triggers when creating BR-XXX, UJ-XXX, API-XXX, or CFD-XXX entries. Outputs formatted SoT entry with validated cross-references.

日本語の概要は準備中です。原文の説明を表示しています。

mattgierhart/PRD-driven-context-engineering1812026年8月31日 更新

Install the PRD-Driven Context Engineering methodology into a fresh OR existing repository — the subscription-native alternative to forking the whole repo. Runs an interactive wizard that seeds the framework (.claude/ hooks, skills, agents, rules, scripts) without clobbering product content. Triggers on "install the methodology", "adopt this into my repo", "self-install", "set up PRD lifecycle here", "onboard existing project". Outputs an installed framework + a verification report.

日本語の概要は準備中です。原文の説明を表示しています。

mattgierhart/PRD-driven-context-engineering1812026年8月31日 更新

Creates new Source of Truth (SoT) files when existing templates don't fit your needs. Triggers on requests to create a new SoT file, add a new artifact type, or when user says "I need to track [X] but there's no SoT for it", "create SoT", "new source of truth". Outputs a properly structured SoT.*.md file with ID prefix, frontmatter, and update protocol.

日本語の概要は準備中です。原文の説明を表示しています。

mattgierhart/PRD-driven-context-engineering1812026年8月31日 更新

Synchronizes README.md Command Center with current project state. Triggers on gate changes, EPIC status changes, or explicit `/ghm-status-sync` invocation. Outputs updated README.md dashboard with current lifecycle stage, blockers, and metrics.

日本語の概要は準備中です。原文の説明を表示しています。

mattgierhart/PRD-driven-context-engineering1812026年8月31日 更新

mattgierhart のスキルをすべて見る

このスキルの問題を報告する