prd-v03-features-value-planning
Feature Value Planning
Position in workflow: v0.3 Commercial Model → v0.3 Feature Value Planning → v0.4 User Journeys
Features are the unit of scope. Every feature must trace back to why it exists: outcome, moat, competitive position, or pricing tier.
Consumes
This skill requires prior work from v0.1-v0.3:
- CFD-* entries (customer feedback, from v0.1-v0.2) — Evidence for what users need/want
- KPI-* entries (outcome definitions, from v0.3 Outcome Definition) — What metrics does each feature support
- BR-* moat entries (from v0.3 Moat Definition) — What features defend our competitive position
- BR-* pricing entries (from v0.3 Pricing Model) — What features differentiate tiers
- Market landscape analysis (from v0.2) — Competitive feature comparison
This skill assumes v0.1-v0.2 research is complete and risk/tech decisions (v0.5) are not yet made.
Produces
More from mattgierhart/prd-driven-context-engineering
prd-v05-technical-stack-selection
Determine technologies needed to build the product, making build/buy/integrate decisions during PRD v0.5 Red Team Review. Handles both greenfield and brownfield contexts. Triggers on requests to select tech stack, evaluate technologies, make build vs. buy decisions, discover existing assets, or when user asks "what technologies?", "select tech stack", "build or buy?", "what do we reuse?", "existing stack", "technical decisions", "what tools do we need?", "evaluate solutions". Consumes FEA- (features), SCR- (screens), RISK- (constraints). Outputs TECH- entries with decisions, rationale, and trade-offs. Feeds v0.6 Architecture Design.
11prd-v09-gtm-strategy
>
8prd-v04-user-journey-mapping
Map user missions from trigger to value moment, organizing features into coherent paths during PRD v0.4 User Journeys. Triggers on requests to map user journeys, define user flows, describe how users accomplish goals, or when user asks "map user journeys", "define user flows", "user missions", "how do users accomplish X?", "journey mapping", "what steps do users take?", "pain to value flow". Consumes PER- (Persona Definition), FEA- (Feature Value Planning), KPI- (Outcome Definition). Outputs UJ- entries with step flows, pain points, and value moments. Feeds v0.4 Screen Flow Definition.
8ghm-gate-check
>
1prd-v06-environment-setup
Document development environment requirements for team consistency and AI agent understanding during PRD v0.6 Architecture. Triggers on requests to define environment setup, document tooling, create dev setup guide, or when user asks "what tools do I need?", "environment setup", "dev environment", "CLI requirements", "project setup", "onboarding setup". Consumes TECH- (stack selections), ARC- (architecture decisions). Outputs ENV- entries for development, CI/CD, and infrastructure environments. Feeds v0.7 Build Execution.
1prd-v09-launch-metrics
>
1