gsd-mvp-phase

Convert a phase roadmap into MVP mode with SPIDR scope validation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/BeiBei-Clic/ai-skills --skill gsd-mvp-phase-beibei-clic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-mvp-phase
Source: https://github.com/BeiBei-Clic/ai-skills/tree/main/gsd-mvp-phase
Command: npx skills add https://github.com/BeiBei-Clic/ai-skills --skill gsd-mvp-phase-beibei-clic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you turn a phase idea into an MVP-ready plan by forcing a clear user story, checking whether the scope is too large, and writing consistent roadmap output for downstream planning.

Core Features & Use Cases

  • Guided MVP-mode user story capture: Collects an “As a / I want to / So that” story via structured prompts to reduce ambiguity.
  • SPIDR-based scope splitting: Checks whether the story is too big and, if needed, walks you through Spike/Paths/Interfaces/Data/Rules and offers to split into multiple phases.
  • Roadmap conversion and delegation: Writes Mode: mvp and a reformatted Goal into the phase’s ROADMAP.md, then delegates to /gsd plan-phase <N> to continue planning with MVP mode.

Quick Start

Run gsd-mvp-phase with your phase number (for example, 2) so it captures the MVP user story, validates scope, updates ROADMAP.md with Mode and Goal, and then generates the plan via /gsd plan-phase 2.

Frequently Asked Questions about gsd-mvp-phase

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

FAQPage Schema
How do I convert an existing phase roadmap into an MVP slice for product execution?

To convert an existing phase roadmap into an MVP slice, the tool captures a structured user story, validates scope using SPIDR splitting, writes MVP mode into ROADMAP.md, and delegates to /gsd plan-phase for downstream planning.

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

SPIDR splitting evaluates whether an MVP user story is too large by examining Spike, Paths, Interfaces, Data, and Rules. You need it when a phase's scope exceeds vertical slice limits and requires division into multiple manageable phases.

How do I write a structured user story for MVP phase planning?

MVP phase planning requires a structured user story in the "As a / I want to / So that" format. The tool uses guided prompts to capture this story, reducing ambiguity before validating scope and writing the phase roadmap.

Do I need existing phases before planning an MVP slice?

Yes, existing phases are required before planning an MVP slice. The workflow applies phase existence and status guarding, meaning you must already have phases defined before converting a specific phase's roadmap into MVP mode.

What's the best way to handle a phase scope that is too large for a single MVP?

When a phase scope is too large for a single MVP, the tool walks you through SPIDR splitting criteria and offers to split the work into multiple phases, ensuring the vertical slice remains viable before writing the roadmap.

Why does my phase roadmap need a mode field for MVP planning?

The phase roadmap needs a mode field set to "mvp" to trigger MVP-specific planning logic. The tool writes Mode: mvp and a reformatted Goal into ROADMAP.md, then delegates to /gsd plan-phase to generate the follow-on plan.