/gsd-mvp-phase
Plan a phase as a vertical MVP slice — user story, SPIDR splitting, then plan-phase
$ npx -y skills add open-gsd/gsd-core --skill gsd-mvp-phase --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/gsd-mvp-phase
Context preview
The summary Claude sees to decide when to auto-load this skill.
Plan a phase as a vertical MVP slice — user story, SPIDR splitting, then plan-phase
SKILL.md
gsd-mvp-phase.SKILL.mdname: gsd-mvp-phase
description: "Plan a phase as a vertical MVP slice — user story, SPIDR splitting, then plan-phase"
argument-hint: "<phase-number>"
allowed-tools:
- Read
- Write
- Bash
- Glob
- Grep
- Agent
- AskUserQuestion
<objective> Guide the user through MVP-mode planning for a phase. The command:
1. Prompts for an "As a / I want to / So that" user story (three structured questions) 2. Runs SPIDR splitting check — if the story is too large, walks through Spike/Paths/Interfaces/Data/Rules and offers to split into multiple phases 3. Writes `**Mode:** mvp` and the reformatted `**Goal:**` to the phase's ROADMAP.md section 4. Delegates to `/gsd plan-phase <N>` which auto-detects MVP mode via the roadmap field
Phase 1 of the vertical-mvp-slice PRD shipped the planner-side machinery; this command is the user entry point for it. </objective>
<execution_context> @~/.claude/gsd-core/workflows/mvp-phase.md @~/.claude/gsd-core/references/spidr-splitting.md @~/.claude/gsd-core/references/user-story-template.md </execution_context>
<runtime_note> **Copilot (VS Code):** Use `vscode_askquestions` wherever this workflow calls `AskUserQuestion`. Equivalent API. </runtime_note>
<context> Phase number: $ARGUMENTS (required — integer or decimal like `2.1`)
The phase must already exist in ROADMAP.md (created via `/gsd new-project`, `/gsd add-phase`, or `/gsd insert-phase`). This command does not create new phases — it converts an existing phase to MVP mode. </context>
<process> Execute the mvp-phase workflow from @~/.claude/gsd-core/workflows/mvp-phase.md end-to-end. Preserve all gates: phase existence, status guard (refuse in_progress/completed), user-story format validation, SPIDR splitting check, ROADMAP write confirmation, plan-phase delegation. </process>
Read more
name: gsd-mvp-phase description: "Plan a phase as a vertical MVP slice — user story, SPIDR splitting, then plan-phase" argument-hint: "<phase-number>" allowed-tools: - Read - Write - Bash - Glob - Grep - Agent - AskUserQuestion
<objective> Guide the user through MVP-mode planning for a phase. The command:
1. Prompts for an "As a / I want to / So that" user story (three structured questions) 2. Runs SPIDR splitting check — if the story is too large, walks through Spike/Paths/Interfaces/Data/Rules and offers to split into multiple phases 3. Writes `**Mode:** mvp` and the reformatted `**Goal:**` to the phase's ROADMAP.md section 4. Delegates to `/gsd plan-phase <N>` which auto-detects MVP mode via the roadmap field
Phase 1 of the vertical-mvp-slice PRD shipped the planner-side machinery; this command is the user entry point for it. </objective>
<execution_context> @~/.claude/gsd-core/workflows/mvp-phase.md @~/.claude/gsd-core/references/spidr-splitting.md @~/.claude/gsd-core/references/user-story-template.md </execution_context>
<runtime_note> **Copilot (VS Code):** Use `vscode_askquestions` wherever this workflow calls `AskUserQuestion`. Equivalent API. </runtime_note>
<context> Phase number: $ARGUMENTS (required — integer or decimal like `2.1`)
The phase must already exist in ROADMAP.md (created via `/gsd new-project`, `/gsd add-phase`, or `/gsd insert-phase`). This command does not create new phases — it converts an existing phase to MVP mode. </context>
<process> Execute the mvp-phase workflow from @~/.claude/gsd-core/workflows/mvp-phase.md end-to-end. Preserve all gates: phase existence, status guard (refuse in_progress/completed), user-story format validation, SPIDR splitting check, ROADMAP write confirmation, plan-phase delegation. </process>
Git. Ship. Done. A light-weight meta-prompting, context engineering, and spec-driven development system for Claude Code, OpenCode, Antigravity CLI, Kimi CLI, Kilo, Codex, Copilot, Cursor, Windsurf, and more.
Repo: open-gsd/gsd-core
Other skills on gsd-core.
- /gsd-add-tests
Generate tests for a completed phase based on UAT criteria and implementation
Open skill - /gsd-ai-integration-phase
Generate an AI-SPEC.md design contract for phases that involve building AI systems.
Open skill - /gsd-audit-fix
Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit
Open skill - /gsd-audit-milestone
Audit milestone completion against original intent before archiving
Open skill - /gsd-audit-uat
Cross-phase audit of all outstanding UAT and verification items
Open skill - /gsd-autonomous
Run all remaining phases autonomously — discuss→plan→execute per phase
Open skill

