pm-mvp-scope

Name: pm-mvp-scope
Availability: InStock
Author: ljucask

Classify prioritized features into MVP, post-MVP, or cut with delivery stripes.

1|Updated May 28, 2026

Search Tags:#prioritization #feature planning #mvp #product roadmap #feature scope #delivery stripes

Ready to run

npx skills add https://github.com/ljucask/pureinn-product-development --skill pm-mvp-scope

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pm-mvp-scope
Source: https://github.com/ljucask/pureinn-product-development/tree/main/skills/pm-mvp-scope
Command: npx skills add https://github.com/ljucask/pureinn-product-development --skill pm-mvp-scope

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams avoid bloated MVPs by turning prioritized features into a clear build decision, separating what ships now from what is deferred or removed.

Core Features & Use Cases

MVP Scope Decisions: Evaluates features against product goals, priorities, dependencies, and constraints to classify them as MVP, post-MVP, or cut.
Delivery Stripe Planning: Organizes approved features into parallel development channels with dependency-aware assignments.
Feature Planning Updates: Maintains consistent phase and stripe information across feature lists, feature cards, and optional product management systems.
Use Case: A product manager preparing for launch can use this Skill to decide which features belong in the first release and create an execution structure for engineering teams.

Quick Start

Use the pm-mvp-scope skill to define the MVP scope and delivery stripes for my prioritized feature list.

Frequently Asked Questions about pm-mvp-scope

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

FAQPage Schema

How do I define MVP scope from a prioritized feature list?▼

You define MVP scope by evaluating features against product goals, dependencies, and constraints to classify them as MVP, post-MVP, or cut. This prevents bloated releases by separating what ships now from deferred or removed items.

What is delivery stripe planning in product roadmaps?▼

Delivery stripe planning organizes approved MVP features into parallel development channels with dependency-aware assignments. It creates an execution structure that maps feature dependencies to specific engineering teams for roadmap preparation.

How do I decide which features to cut or defer for an MVP launch?▼

You decide by applying dependency-aware feature evaluation against product goals and constraints. This classifies features into MVP inclusion, post-MVP deferral, or removal from the current product roadmap to ensure a focused launch scope.

Can I use this for phase-based MVP tracking and feature planning updates?▼

Yes, you can use it for phase-based MVP tracking. It maintains consistent phase and stripe information across feature lists and feature cards, requiring dependency-aware evaluation and approval-driven workflow execution to update artifacts.

What's the best way to avoid a bloated MVP when preparing a product roadmap?▼

The best way to avoid a bloated MVP is turning prioritized features into a clear build decision. By evaluating constraints and dependencies, you separate what ships now from what is deferred, ensuring focused delivery paths.