gsd-mvp-phase

Convert a user story into a validated MVP-mode roadmap phase.

Updated May 21, 2026
One-click install
npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-mvp-phase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-mvp-phase
Source: https://github.com/jedmamosto/m-and-ms/tree/main/.agents/skills/gsd-mvp-phase
Command: npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-mvp-phase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a rough MVP idea into a validated, properly structured phase plan, reducing the risk of building the wrong slice or an overly large “phase” that should be split.

Core Features & Use Cases

  • User-story-first phase planning: Prompts for a clean “As a / I want to / So that” user story using structured questions, ensuring the goal is clear and testable.
  • SPIDR splitting guardrail: Checks whether the story is too large and, when needed, walks through Spike/Paths/Interfaces/Data/Rules to help you split into multiple phases.
  • Roadmap MVP mode + delegation: Writes the phase as Mode: mvp and updates the phase Goal, then delegates to the phase planner so the plan is generated in MVP mode.

Quick Start

Run the command /gsd mvp-phase 2 after making sure phase 2 already exists in ROADMAP.md.

Frequently Asked Questions about gsd-mvp-phase

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

FAQPage Schema
How do I plan an MVP slice from a user story?

MVP phase planning converts a user story into validated roadmap content by checking scope with SPIDR splitting, writing Mode: mvp to the roadmap, and delegating to a phase planner for execution.

What is SPIDR splitting and when do I need it for MVP planning?

SPIDR splitting analyzes Spike, Paths, Interfaces, Data, and Rules to break down overly large user stories into multiple manageable MVP phases, preventing bloated scope during product discovery.

How do I validate if my user story is too large for a single MVP phase?

Validate story scope by applying a SPIDR splitting guardrail, which checks the user-story format and walks through Spike/Paths/Interfaces/Data/Rules to determine if the phase requires splitting.

Do I need an existing roadmap phase before planning a vertical MVP slice?

Yes, MVP phase planning requires a phase to already exist in ROADMAP.md with proper status guards before it can write the Mode and Goal updates for the vertical slice.

What's the best way to structure a user story for MVP mode roadmap updates?

Structure the user story using the “As a / I want to / So that” format to ensure the goal is clear and testable, which allows the roadmap to properly update Mode: mvp and the phase Goal.

Why does my MVP phase planning fail when the user story format is invalid?

MVP phase planning fails without user-story format validation because it relies on a clean “As a / I want to / So that” structure to generate the phase plan and write roadmap updates correctly.