gsd-mvp-phase

Convert project phases into vertical MVP slices via SPIDR splitting.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/nnexai/git-stacks --skill gsd-mvp-phase-nnexai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-mvp-phase
Source: https://github.com/nnexai/git-stacks/tree/main/.codex/skills/gsd-mvp-phase
Command: npx skills add https://github.com/nnexai/git-stacks --skill gsd-mvp-phase-nnexai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the challenge of scope creep and bloated project planning by enforcing a vertical MVP (Minimum Viable Product) approach to phase development.

Core Features & Use Cases

  • Structured Storytelling: Guides users through the As a / I want to / So that framework to ensure clear requirements.
  • SPIDR Splitting: Automatically checks if a story is too large and offers to split it into manageable spikes, paths, interfaces, data, or rules.
  • Workflow Integration: Seamlessly updates project ROADMAP.md files and delegates to the gsd plan-phase engine for execution.

Quick Start

Invoke the gsd-mvp-phase skill followed by the phase number to begin the interactive MVP planning process for your project.

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 project phases as vertical MVP slices to prevent scope creep?

To plan project phases as vertical MVP slices, you convert phase scope into validated user stories using the As a / I want to / So that framework, ensuring minimal viable delivery against the project roadmap.

What is SPIDR splitting in agile user story planning?

SPIDR splitting is an agile planning technique that breaks down oversized user stories into manageable spikes, paths, interfaces, data, or rules to maintain vertical MVP scope during software development.

How do I validate user stories against a project roadmap for agile development?

You validate user stories against a project roadmap by structuring requirements through the As a / I want to / So that framework and ensuring phase lifecycle management aligns with existing ROADMAP.md documentation.

Can I integrate MVP phase planning directly with my existing ROADMAP.md files?

Yes, MVP phase planning integrates with existing ROADMAP.md files by updating them directly and delegating execution to the gsd plan-phase engine to ensure consistent phase lifecycle management.

Do I need a GSD workflow engine to manage vertical MVP slices?

Yes, managing vertical MVP slices requires integration with a GSD workflow engine and existing ROADMAP.md documentation to ensure structured phase lifecycle management and consistent execution.

When should I split user stories during software development planning?

You should split user stories during software development planning when a story is automatically detected as too large, using SPIDR splitting to divide it into manageable spikes, paths, interfaces, data, or rules.