prd-v03-features-value-planning_skill

Overview

This skill defines and prioritizes product features with strategic traceability during PRD v0.3 Commercial Model. It produces FEA- entries that map each feature to KPIs, moat rules, pricing tiers, and competitor context. Outputs feed v0.4 User Journeys and enforce BR-FEA governance for consistent decisions.

How this skill works

On requests like “what features do we build?” it ingests KPI-, BR-, and CFD- entries from v0.3 and classifies features by Type (Moat, Outcome, Parity, Delta, Tier, Table Stakes). It assigns priority tiers (P0–P3), generates FEA- templates with validation and acceptance criteria, and emits BR-FEA governance rules to enforce traceability and gating. It flags anti-patterns and scope risks for corrective action.

When to use it

• Defining which features to include in MVP or launch scope
• Prioritizing capabilities against KPIs, moat rules, and pricing tiers
• Mapping features to pricing tiers and competitor parity/delta
• Scoping a product for v0.4 User Journeys based on v0.3 analysis
• When asked “what’s in MVP?” or “which features matter?”

Best practices

• Require KPI- or BR- linkage for P0/P1 features (Outcome Link Required)
• Validate P0 features with CFD- evidence before building (Validation Before Build)
• Enforce parity-first for Fast Follow products (BR-FEA-PARITY-FIRST)
• Keep P2/P3 under 40% of scope; cut or defer if exceeded
• Write acceptance criteria as testable conditions tied to outcome metrics

Example use cases

• Generate FEA- entries for a candidate feature list and map each to KPI-, BR-, CFD- references
• Run a parity vs. delta analysis to decide which competitor features must be matched before differentiation
• Scope an MVP: assign P0/P1 to outcome and moat features and move table stakes to lower tiers
• Create BR-FEA rules to prevent scope creep and require validation gates before development