pm-mvp-scope

When to use

Phase 5, after pm-features-list is approved and (optionally) pm-prioritize has run. This is the Phase 5 exit artifact. pm-stripe uses the output of this skill to orchestrate the JIT build cycle.

---

What it produces

Two updates to existing artifacts (not new files):

1. phase field per feature in feature_list.md and each Feature Card frontmatter:

   • MVP (or project's first phase label, e.g. P0) = in scope for MVP
   • MVP+ or later phase = post-MVP
   • Removed from list = cut

2. stripe field per feature in feature_list.md and each Feature Card frontmatter:

   • Assigns each feature to a Delivery Stripe (parallel development channel)
   • Example: stripe-checkout, stripe-auth, stripe-notifications
   • Stripe = domain-coherent delivery channel; one feature active per stripe at a time

After user approval: updates Notion Feature entries with phase and stripe values.

---

How to invoke

/pm-mvp-scope           # interactive
/pm-mvp-scope --agent   # autonomous draft, requires review before finalizing

---

The phase field is the single source of truth for MVP membership

Never use a separate mvp: true/false flag. MVP membership is recorded in phase. Two fields on the same axis drift apart.

---

Delivery Stripes

Stripes are parallel domain-focused development channels. Each stripe operates independently - one feature active per stripe at a time, progressing through the JIT cycle.

Stripe assignment rules:

• Features in one stripe must belong to a coherent domain slice
• A feature cannot be assigned to a stripe where one of its dependencies is in a different stripe still in progress
• Cross-stripe dependencies are surfaced as risks before finalizing assignment

How stripes work in Phase 6: pm-stripe orchestrates the JIT cycle per stripe - picking the next ready feature and routing it through pm-feature-design → build → review → shipped. See docs/phase-6-build/pm-stripe.md.

---

When features already carry a phase (Rebuild)

If features already carry phase assignments from pm-product-roadmap (e.g., a Rebuild where roadmap split into P0 Pilot / P1 / P2):

• The MVP cut is already decided - do NOT re-litigate IN/POST
• This skill's job is only stripe assignment
• Confirm the phase-derived cut with the user, then assign stripes

---

Dependencies

Required before running:

• pm-features-list - must include Dependency Map, KANO Analysis, and V×C Matrix (all approved)

Recommended:

• pm-prioritize - recommended to run before MVP scope if priority order has been updated
• pm-kpis - North Star and AARRR metrics validate MVP scope alignment
• pm-business-case - revenue model and runway inform how aggressive the MVP cut should be

Produces for:

• features/feature_list.md - phase and stripe updated per feature
• /features/cards/FEAT-*.md - phase and stripe fields updated in each Feature Card
• pm-product-roadmap (v3) - delivery view populated with stripe and phase data
• pm-stripe - uses stripe assignments to orchestrate the JIT cycle per stripe

Related skills: pm-features-list, pm-prioritize, pm-product-roadmap, pm-stripe