Feature Value Planning: Stop Guessing What Goes in the MVP

Where this fits

Your commercial model is taking shape in PRD v0.3: KPI entries define outcomes, BR entries define pricing and moat, and CFD entries capture customer feedback. You still need to decide what features belong in the MVP, which ones differentiate, and which are just parity. This skill turns that decision into a traceable step by consuming those v0.3 artifacts and emitting FEA- entries with governance rules that feed v0.4 user journeys.

Why agents benefit

• Recognizes feature-planning triggers like "what's in MVP?", "parity features", and "what's our delta?" so the agent switches from drafting prose to producing structured FEA- entries.
• Grounds every feature proposal in existing KPI-, BR-, and CFD- entries, so priorities come from evidence instead of guesswork.
• Distinguishes parity from delta features while enforcing the pricing model and moat defined earlier in v0.3.
• Creates BR-FEA governance rules that keep future feature additions consistent with the commercial strategy.
• Passes a structured feature set to v0.4 user journey work, preserving context across the PRD pipeline.

Practical scenarios

Scoping the MVP from evidence

The agent reviews CFD- feedback and KPI targets, clusters capabilities into must-have versus defer, and outputs MVP FEA- entries with explicit reasoning. The PM can see exactly why each feature is in scope.

Mapping features to pricing tiers

The agent takes the BR pricing model and maps features to Free, Pro, and Enterprise tiers. Priceable delta features are marked as premium, while parity features stay in the base tier, preventing accidental premium placement.

Auditing parity vs. delta before a competitor launch

A prompt like "what's our delta?" triggers the agent to compare CFD and moat analysis, tag parity and delta features, and propose governance rules to prevent future features from eroding the moat.

Add it to your agent workflow

Install with:

npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v03-features-value-planning

Then prompt:

I have KPI-, BR-, and CFD-* entries from v0.3. Define our feature set, scope MVP, map features to pricing tiers, and identify parity vs. delta features.

The skill reads the available context and returns FEA- entries ready for v0.4 user journeys.

Compare before adopting

Before adding it, compare against generic feature prioritization skills by looking at README maintenance freshness, output format compatibility, and whether it handles your artifact naming conventions. The repo's star count and issue activity are useful signals, but the skill's real value is workflow fit. You can review the workflow fit and quality signals on the skill's OpenAgentSkill page: https://www.openagentskill.com/skills/mattgierhart-prd-v03-features-value-planning

Why it is worth tracking

With 182 stars and clear positioning between v0.3 Commercial Model and v0.4 User Journeys, this skill represents a reusable pattern for feature-value traceability. It is worth tracking if you are standardizing PRD generation in agent workflows and need evidence-based feature decisions. Re-evaluate when the repository adds support for new artifact versions or strengthens its governance rules.