How do I install the Gsd:mvp Phase skill?

Run npx skillmds@latest add majiayu000/gsd-mvp-phase in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gsd:mvp Phase safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gsd:mvp Phase?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gsd:mvp Phase free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gsd:mvp Phase?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gsd:mvp Phase by majiayu000 — Agent Skill

Name: Gsd:mvp Phase
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Orchestrator role: Parse phase argument, validate phase, gather user story, run SPIDR check, persist mode + story to ROADMAP.md, then route to plan-phase.

TEXT_MODE fallback: Set TEXT_MODE=true if --text is present in $ARGUMENTS OR text_mode from init JSON is true. When TEXT_MODE is active, replace every AskUserQuestion call with a plain-text numbered list and ask the user to type their choice number.

Flags:

--force — Allow operating on in_progress / completed phases
--text — Use plain-text numbered lists instead of TUI menus

Show MVP-planning status (e.g., ## ✓ Phase N MVP-Planned — vertical slice captured)
Emit a ## ▶ Next Up heading with /gsd:execute-phase N (TDD execution)
Use `/clear` then: before the command
Include a parenthetical: (/clear is safe — /gsd:resume-work restores position from HANDOFF.json if you change your mind)

MVP planning is a deliberate slice-of-the-cake exercise; clearing context before execution keeps TDD focused on the captured story rather than the planning conversation.

---name: gsd-mvp-phasedescription: Plan an MVP-mode phase — captures an "As a / I want to / So that" user story, runs SPIDR splitting, then delegates to plan-phase---<objective> Guide the user through MVP-mode planning for a phase. Prompts for an "As a / I want to / So that" user story, runs SPIDR splitting check on the story, writes the result to ROADMAP.md, and delegates to `/gsd:plan-phase` (which auto-detects MVP via the roadmap mode field). **Orchestrator role:** Parse phase argument, validate phase, gather user story, run SPIDR check, persist mode + story to ROADMAP.md, then route to plan-phase. </objective> <execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/mvp-phase.md @${CLAUDE_PLUGIN_ROOT}/references/user-story-template.md @${CLAUDE_PLUGIN_ROOT}/references/spidr-splitting.md @${CLAUDE_PLUGIN_ROOT}/references/planner-mvp-mode.md </execution_context> <runtime_note> **Copilot (VS Code):** Use `vscode_askquestions` wherever this workflow calls `AskUserQuestion`. They are equivalent — `vscode_askquestions` is the VS Code Copilot implementation of the same interactive question API. **TEXT_MODE fallback:** Set TEXT_MODE=true if `--text` is present in `$ARGUMENTS` OR `text_mode` from init JSON is true. When TEXT_MODE is active, replace every AskUserQuestion call with a plain-text numbered list and ask the user to type their choice number. </runtime_note> <context> Phase number: $ARGUMENTS (required — integer or decimal like `2.1`) **Flags:** - `--force` — Allow operating on `in_progress` / `completed` phases - `--text` — Use plain-text numbered lists instead of TUI menus </context> <process> Execute the mvp-phase workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/mvp-phase.md end-to-end. Preserve all workflow gates (phase validation, user-story prompt, SPIDR check, ROADMAP.md persistence, delegation to plan-phase). </process> <output_format> When MVP planning concludes (user story written, ROADMAP.md updated, plan-phase delegated), emit a Next Up continuation block following the pattern in `references/continuation-format.md`: - Show MVP-planning status (e.g., `## ✓ Phase N MVP-Planned — vertical slice captured`) - Emit a `## ▶ Next Up` heading with `/gsd:execute-phase N` (TDD execution) - Use **`` `/clear` then: ``** before the command - Include a parenthetical: *(`/clear` is safe — `/gsd:resume-work` restores position from `HANDOFF.json` if you change your mind)* MVP planning is a deliberate slice-of-the-cake exercise; clearing context before execution keeps TDD focused on the captured story rather than the planning conversation. </output_format>

Frequently asked questions

Gsd:mvp Phase