prd-v03-features-value-planning

Define and prioritize product features with strategic traceability for PRD v0.3.

193|9|Updated Jul 10, 2025
One-click install
npx skills add https://github.com/mattgierhart/PRD-driven-context-engineering --skill prd-v03-features-value-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-v03-features-value-planning
Source: https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v03-features-value-planning
Command: npx skills add https://github.com/mattgierhart/PRD-driven-context-engineering --skill prd-v03-features-value-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Define and prioritize product features with robust traceability during PRD v0.3, enabling deterministic alignment to outcomes, moats, and pricing strategies.

Core Features & Use Cases

  • Framework for classifying features (Moat, Outcome, Parity, Delta, Tier, Table Stakes) and the required evidence (KPI-, CFD-, BR- links).
  • Automated generation of FEA- entries with governance rules and downstream connections to v0.4 User Journeys.
  • Clear traceability from feature requests to implementation artifacts and metrics.

Quick Start

Provide a PRD v0.3 feature request to generate FEA- entries.

Frequently Asked Questions about prd-v03-features-value-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize product features with strategic traceability in a PRD?

Prioritize product features by classifying them as Moat, Outcome, Parity, Delta, or Table Stakes, then linking each to KPI, CFD, and governance evidence. This ensures deterministic alignment between feature requests, pricing tiers, and implementation artifacts.

What is the best way to map features to pricing tiers and scope an MVP?

Map features to pricing tiers and scope MVP by evaluating parity versus delta capabilities, then assigning features to specific tiers with required evidence links. This framework ensures only strategically aligned features enter the MVP scope.

How do I generate FEA entries that satisfy governance and traceability rules?

Generate FEA entries by processing PRD v0.3 feature requests through the governance framework, which automatically applies BR-FEA rules and establishes traceability links to KPI and CFD metrics for downstream user journey mapping.

Can I use this feature planning framework to identify moat versus table stakes capabilities?

Yes, classify features into categories like Moat, Table Stakes, Parity, and Delta to distinguish competitive advantages from baseline requirements. This classification requires linking evidence to KPI and CFD metrics for governance validation.

When do I need PRD v0.3 feature planning and what downstream artifacts does it connect to?

PRD v0.3 feature planning is needed when defining product capabilities, scoping MVPs, or mapping features to tiers. It generates FEA entries that connect downstream to v0.4 User Journeys for implementation traceability.

Does feature traceability work without KPI and CFD evidence links?

No, governance rules require KPI and CFD evidence links for each classified feature to maintain traceability. Without these links, FEA entries cannot satisfy BR-FEA governance requirements or connect to downstream user journeys.