Plan a phase as a vertical MVP slice — user story, SPIDR splitting, then plan-phase
Scanned 9/2/2026
Install to Claude Code
npx -y skills add friday-ai-codes/friday-ai --skill gsd-mvp-phase --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Gsd Mvp Phase?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/friday-ai-codes-gsd-mvp-phase)More formats (shields.io, HTML) on the badges page.
---
name: gsd-mvp-phase
description: "Plan a phase as a vertical MVP slice — user story, SPIDR splitting, then plan-phase"
---
<cursor_skill_adapter>
## A. Skill Invocation
- This skill is invoked when the user mentions `gsd-mvp-phase` or describes a task matching this skill.
- Treat all user text after the skill mention as `{{GSD_ARGS}}`.
- If no arguments are present, treat `{{GSD_ARGS}}` as empty.
## B. User Prompting
When the workflow needs user input, prompt the user conversationally:
- Present options as a numbered list in your response text
- Ask the user to reply with their choice
- For multi-select, ask for comma-separated numbers
## C. Tool Usage
Use these Cursor tools when executing GSD workflows:
- `Shell` for running commands (terminal operations)
- `StrReplace` for editing existing files
- `Read`, `Write`, `Glob`, `Grep`, `Task`, `WebSearch`, `WebFetch`, `TodoWrite` as needed
## D. Subagent Spawning
When the workflow needs to spawn a subagent:
- Use `Task(subagent_type="generalPurpose", ...)`
- The `model` parameter maps to Cursor's model options (e.g., "fast")
</cursor_skill_adapter>
<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>
@/Users/zaneliu/Projects/open-source/friday-ai/.cursor/gsd-core/workflows/mvp-phase.md
@/Users/zaneliu/Projects/open-source/friday-ai/.cursor/gsd-core/references/spidr-splitting.md
@/Users/zaneliu/Projects/open-source/friday-ai/.cursor/gsd-core/references/user-story-template.md
</execution_context>
<runtime_note>
**Copilot (VS Code):** Use `vscode_askquestions` wherever this workflow calls `conversational prompting`. Equivalent API.
</runtime_note>
<context>
Phase number: {{GSD_ARGS}} (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 @/Users/zaneliu/Projects/open-source/friday-ai/.cursor/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>
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!