pm-mvp-scopelisted

Define MVP scope and delivery plan from the prioritized FDD Feature List. Makes the IN/POST-MVP/CUT decision per feature (recorded in the single `phase` field, never a separate `mvp` flag), assigns each feature to a Delivery Stripe. Updates feature_list.md and Feature Card frontmatter (phase + stripe). If features already carry a phase (Rebuild where roadmap split phases), reads it instead of re-deciding the cut and only assigns stripes. After user approval, updates Notion Feature entries with phase and stripe assignment. Phase 5 exit artifact. Required input for pm-stripe JIT cycle.
ljucask/pureinn-product-development · ★ 1 · AI & Automation · score 77

Install: claude install-skill ljucask/pureinn-product-development

# PM - MVP Scope ## Agent mode (`--agent`) Supports `--agent`: runs autonomously in a subagent, drafts the artifact from existing inputs, and returns a short summary + coverage note. - **No flag** → interactive (default); if inputs are heavy, offer agent mode. - **`--agent`** → obey. First check inputs are complete. Anything missing: do NOT invent it - mark `[ASSUMED - what/why]` in the output and summary. Never hallucinate to fill a gap. - **Review required:** the artifact contains commitments - after drafting, require the user's review before finalizing; do not close decisions autonomously. --- ## What this skill does Phase 5 / Steps 4-5. Takes the prioritized, dependency-mapped FDD Feature List (Live Register 4, output of `pm-features-list`) and produces the delivery structure: 1. **MVP Scope Decision** - what is IN (MVP), what is POST-MVP, what is CUT. Decision is **per Feature** - not per Feature Set. Feature Sets are grouping only and do not affect the MVP cut. **MVP membership is recorded in the `phase` field, NOT a separate `mvp` boolean** - see the next section. 2. **Delivery Stripes** - parallel development tracks (not time-boxed sprints). Each stripe is an isolated channel for a coherent domain slice (e.g., stripe-checkout, stripe-auth). Features are assigned to stripes based on domain affinity and dependencies. 3. **Stripe assignment** - updates `stripe:` field in each Feature Card frontmatter and in feature_list.md. After user approval: update Notion Fea