Prd V09 Gtm Strategy logo

Prd V09 Gtm Strategy

Community
mattgierhart
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.

Overview

Publishermattgierhart
RepositoryPRD-driven-context-engineering
Skill nameprd-v09-gtm-strategy
Stars
179
Forks
11
Bundled files
5
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 5 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by mattgierhart on GitHub. Read the source before you install it.

Installation

Install the Prd V09 Gtm Strategy AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineering.git /tmp/PRD-driven-context-engineering
mkdir -p .claude/skills
cp -r /tmp/PRD-driven-context-engineering/plugins/prd-ce/skills/prd-v09-gtm-strategy .claude/skills/prd-v09-gtm-strategy
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Prd V09 Gtm Strategy in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Prd V09 Gtm Strategy on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Prd V09 Gtm Strategy is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Prd V09 Gtm Strategy AI skill do?

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.

Why use Prd V09 Gtm Strategy on TypingMind?

Because you install it once and use it with any model. Prd V09 Gtm Strategy is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Prd V09 Gtm Strategy in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/plugins/prd-ce/skills/prd-v09-gtm-strategy. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Prd V09 Gtm Strategy?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Prd V09 Gtm Strategy?

As many as you like. As long as a model supports skills, you can use Prd V09 Gtm Strategy with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Prd V09 Gtm Strategy AI skill free?

Yes. It is published on GitHub by mattgierhart under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇