plugins/gsd/skills/mvp-phase/SKILL.md
Plan an MVP-mode phase — captures an "As a / I want to / So that" user story, runs SPIDR splitting, then delegates to plan-phase
npx skillsauth add davepoon/buildwithclaude gsd:mvp-phaseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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>
Flags:
--force — Allow operating on in_progress / completed phases--text — Use plain-text numbered lists instead of TUI menus
</context>
<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:
## ✓ Phase N MVP-Planned — vertical slice captured)## ▶ Next Up heading with /gsd:execute-phase N (TDD execution)`/clear` then: before the command/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>
tools
Assesses the current state of the startup project and recommends what to focus on next. Use when there is a need or a question from the user to understand what the next steps are or what to focus on next.
data-ai
Use at the start of any conversation about a startup idea, product validation, founder strategy, or work inside a `startup/` workspace. Establishes file conventions, voice-input handling, subagent dispatch rules, and how to update each artifact safely. Activate before invoking any other startup-superpowers skill.
tools
Manages the founder's survey-based validation — crafting the right questions, deploying a survey to the internet, and analyzing results against hypotheses. Use when the founder wants to run a survey, create survey questions, validate hypotheses at scale, check how a survey is going, understand whether a survey is the right tool right now, or deploy a question set to get quantitative signal. Also bring this up if you believe that creating a survey to collect quantitative evidence may be useful at this point.
development
Guides the founder through designing and optionally building the simplest MVP or prototype that validates their current hypotheses. Use when the founder wants to build something to test assumptions, discusses what to build next, wants to interpret results from a live MVP, or is deciding whether the current approach is still right. Also use when a founder proposes something to build — the skill will check whether the proposed form is the simplest thing that generates honest signal.