SKILL_TEMPLATE
[1-2 sentence description of what this skill does]. Triggers on [specific phrases/contexts that should activate this skill]. Outputs [what the skill produces].
Define product positioning using April Dunford's 5-step framework during PRD v0.9 Go-to-Market. Triggers on requests to position the product, define category, frame against competitors, or when user asks "what category are we?", "how do we position?", "Dunford positioning",
$ npx -y skills add mattgierhart/PRD-driven-context-engineering --skill prd-v09-positioning-dunford --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/prd-v09-positioning-dunfordContext preview
The summary Claude sees to decide when to auto-load this skill.
Define product positioning using April Dunford's 5-step framework during PRD v0.9 Go-to-Market. Triggers on requests to position the product, define category, frame against competitors, or when user asks "what category are we?", "how do we position?", "Dunford positioning",
name: prd-v09-positioning-dunford description: > Define product positioning using April Dunford's 5-step framework during PRD v0.9 Go-to-Market. Triggers on requests to position the product, define category, frame against competitors, or when user asks "what category are we?", "how do we position?", "Dunford positioning", "obviously awesome", "market frame of reference", "positioning statement". Outputs GTM-* entries with Type=Positioning and BR-POS-* positioning rules. context: fork allowed-tools: - Read - Write - Edit - Glob - Grep - WebSearch execution_modes: default: standard supports: [quick, standard, deep]
Position in workflow: v0.8 Monitoring Setup → **v0.9 Positioning (Dunford)** → v0.9 Offer Construction (Hormozi) → v0.9 Launch Channels (ORB)
Default is **standard**. See [`.claude/rules/08-skill-execution-modes.md`](../../rules/08-skill-execution-modes.md) for selection logic.
| Mode | What this skill produces | |------|--------------------------| | **quick** | One positioning statement; one best-fit segment; one category claim | | **standard** | Full 5 steps; one segment + ≥3 alternatives + 3–5 attributes mapped to value; category claim with frame of reference | | **deep** | Multiple segment variants; A/B positioning candidates to test; competitor positioning teardown; "best-fit" disqualification rules |
From *Obviously Awesome: How to Nail Product Positioning* (April Dunford, 2019). Positioning is **the act of deliberately defining how you are the best at something a defined market cares a lot about** — not a feature list, not a tagline, not your founder's story.
The five steps run in order:
1. **Competitive alternatives** — What would your customers use if you did not exist? (Status-quo wins as often as competitor products do.) 2. **Unique attributes** — What capabilities or qualities do *you* have that those alternatives don't? 3. **Value (and proof)** — Translate each attribute into the value it delivers to a customer. Anchor in evidence, not aspiration. 4. **Customers who care a lot** — Among all possible buyers, which segment cares *most* about that value? This is your "best-fit" target. 5. **Market category** — Pick the category (the **frame of reference**) that puts your unique strengths at the center and is intelligible to your best-fit customer.
A 6th step (**relevant trends**) is optional and used only when a current market trend reinforces the positioning. Skip it in quick mode.
The work product is a **positioning statement** plus a small set of **positioning rules** that downstream skills (Offer Construction, Launch Channels, GTM messaging) must honor.
This skill assumes v0.2 (competitive landscape, product type) and v0.4 (personas) are complete.
Confidence guidance per P4: a positioning statement should reach **3/5** before downstream skills consume it (i.e., grounded in actual customer interviews, not internal opinion). Quick mode may produce 2/5 outputs but must tag them.
Run the five steps in order. Each step has a single deliverable.
Inventory CFD- entries that name alternatives. Include the status quo ("spreadsheet + email"), not just competitor products. Cluster into 2–4 alternative categories.
**Deliverable**: A ranked list of competitive alternatives with rough usage volume estimates.
For each FEA- you ship, ask: "Does this alternative have it? At this quality?" Keep only attributes that are demonstrably *yours*. Quick mode picks the top 3.
**Deliverable**: 3–5 attributes that are uniquely yours vs. the alternatives.
For each attribute, write the value it creates *for the customer*. Anchor in CFD- evidence (interview quotes, beta data, usage metrics). Mark each value claim with a confidence score.
**Deliverable**: An attribute → value table with evidence and confidence per row.
Cross-reference the value claims against your PER- personas. Which persona's pains are *most* addressed by your unique values? That is your best-fit segment. Write a "best-fit characteristics" list (firmographics, behaviors, triggers).
**Deliverable**: One sharpened best-fit PER- variant with "ideal customer" characteristics.
Choose the **frame of reference** — the category that puts your strengths at the center and is meaningful to your best-fit customer. Test against three checks:
PRD-Led Context Engineering — Memory as Infrastructure. An ontology layer for product teams building products that solve real problems — with AI agents that remember. Gated PRD, typed IDs, markdown knowledge graph, Claude Code skills & hooks.
Repo: mattgierhart/PRD-driven-context-engineering
[1-2 sentence description of what this skill does]. Triggers on [specific phrases/contexts that should activate this skill]. Outputs [what the skill produces].
Validates gate criteria before PRD lifecycle advancement by delegating to the readiness scoring pipeline (scripts/readiness.py). Returns a graduated PASS /…
Extracts durable insights from temp/ files to SoT during EPIC Phase E. Triggers at EPIC completion or explicit `/ghm-harvest` invocation. Outputs new SoT…
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…
Install the PRD-Driven Context Engineering methodology into a fresh OR existing repository — the subscription-native alternative to forking the whole repo.…
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,…