gsd-mvp-phase
Plans development phases as vertical MVP slices to ensure focused delivery.
Install
mkdir -p .claude/skills/gsd-mvp-phase && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12567" && unzip -o skill.zip -d .claude/skills/gsd-mvp-phase && rm skill.zipInstalls to .claude/skills/gsd-mvp-phase
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Plan a phase as a vertical MVP slice — user story, SPIDR splitting, then plan-phaseKey capabilities
- →Prompt for a user story in "As a / I want to / So that" format
- →Run SPIDR splitting check on user stories
- →Offer to split large user stories into multiple phases
- →Write MVP mode and goal to ROADMAP.md
- →Delegate to plan-phase for further planning
How it works
The skill prompts for a user story, checks its size using SPIDR splitting, and if appropriate, updates the ROADMAP.md for MVP planning and delegates to the plan-phase skill.
Inputs & outputs
When to use gsd-mvp-phase
- →Plan project milestones
- →Split user stories into MVP chunks
- →Define phase objectives
About this skill
<codex_skill_adapter>
A. Skill Invocation
- This skill is invoked by mentioning
$gsd-mvp-phase. - Treat all user text after
$gsd-mvp-phaseas{{GSD_ARGS}}. - If no arguments are present, treat
{{GSD_ARGS}}as empty.
B. AskUserQuestion → request_user_input Mapping
GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:
Parameter mapping:
header→headerquestion→question- Options formatted as
"Label" — description→{label: "Label", description: "description"} - Generate
idfrom header: lowercase, replace spaces with underscores
Batched calls:
AskUserQuestion([q1, q2])→ singlerequest_user_inputwith multiple entries inquestions[]
Multi-select workaround:
- Codex has no
multiSelect. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.
Execute mode fallback:
- When
request_user_inputis rejected or unavailable, you MUST stop and present the questions as a plain-text numbered list, then wait for the user's reply. Do NOT pick a default and continue (#3018). - You may only proceed without a user answer when one of these is true:
(a) the invocation included an explicit non-interactive flag (
--autoor--all), (b) the user has explicitly approved a specific default for this question, or (c) the workflow's documented contract says defaults are safe (e.g. autonomous lifecycle paths). - Do NOT write workflow artifacts (CONTEXT.md, DISCUSSION-LOG.md, PLAN.md, checkpoint files) until the user has answered the plain-text questions or one of (a)-(c) above applies. Surfacing the questions and waiting is the correct response — silently defaulting and writing artifacts is the #3018 failure mode.
C. Task() → spawn_agent Mapping
GSD workflows use Task(...) (Claude Code syntax). Translate to Codex collaboration tools:
Direct mapping:
Task(subagent_type="X", prompt="Y")→spawn_agent(agent_type="X", message="Y")Task(model="...")→ omit.spawn_agenthas no inlinemodelparameter; GSD embeds the resolved per-agent model directly into each agent's.tomlat install time somodel_overridesfrom.planning/config.jsonand~/.gsd/defaults.jsonare honored automatically by Codex's agent router.fork_context: falseby default — GSD agents load their own context via<files_to_read>blocksTask(isolation="worktree")/Agent(isolation="worktree")→ no direct Codex mapping. Codexspawn_agentdoes not create or bind a git worktree automatically. Workflows that require this isolation must fail closed or use an explicit manual worktree protocol before spawning (#3360).
Spawn restriction:
- Codex restricts
spawn_agentto cases where the user has explicitly requested sub-agents. When automatic spawning is not permitted, do the work inline in the current agent rather than attempting to force a spawn.
Parallel fan-out:
- Spawn multiple agents → collect agent IDs →
wait(ids)for all to complete
Result parsing:
- Look for structured markers in agent output:
CHECKPOINT,PLAN COMPLETE,SUMMARY, etc. close_agent(id)after collecting results from each agent </codex_skill_adapter>
- Prompts for an "As a / I want to / So that" user story (three structured questions)
- Runs SPIDR splitting check — if the story is too large, walks through Spike/Paths/Interfaces/Data/Rules and offers to split into multiple phases
- Writes
**Mode:** mvpand the reformatted**Goal:**to the phase's ROADMAP.md section - 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/lmarques/Dev/efx-mux/.codex/get-shit-done/workflows/mvp-phase.md @/Users/lmarques/Dev/efx-mux/.codex/get-shit-done/references/spidr-splitting.md @/Users/lmarques/Dev/efx-mux/.codex/get-shit-done/references/user-story-template.md </execution_context>
<runtime_note>
Copilot (VS Code): Use vscode_askquestions wherever this workflow calls AskUserQuestion. Equivalent API.
</runtime_note>
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>
When not to use it
- →When the phase does not already exist in ROADMAP.md
- →When the user story is not intended for MVP planning
Limitations
- →Requires the phase to already exist in ROADMAP.md
- →Refuses to proceed if the phase is in_progress or completed
- →Requires user story format validation
How it compares
This skill guides the user through MVP-mode planning by structuring user story input and applying SPIDR splitting, unlike manually breaking down features.
Compared to similar skills
gsd-mvp-phase side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| gsd-mvp-phase (this skill) | 0 | 3mo | No flags | Intermediate |
| planning-with-files | 233 | 6mo | Review | Intermediate |
| trello | 41 | 2mo | Review | Beginner |
| pmbok-project-management | 38 | 9mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by electroheadfx
View all by electroheadfx →You might also like
planning-with-files
davila7
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
trello
openclaw
Manage Trello boards, lists, and cards via the Trello REST API.
pmbok-project-management
jgtolentino
Comprehensive PMP/PMBOK project management methodologies and best practices. Use this skill when users need guidance on project management processes, templates, knowledge areas, process groups, tools, techniques, or certification preparation. Covers all 10 PMBOK Knowledge Areas and 5 Process Groups with practical templates, frameworks, and industry-standard approaches. Includes risk management, stakeholder engagement, schedule management, cost control, quality assurance, and resource planning.
clickup
civitai
Interact with ClickUp tasks and documents - get task details, view comments, create and manage tasks, create and edit docs. Use when working with ClickUp task/doc URLs or IDs.
ma-playbook
alirezarezvani
M&A strategy for acquiring companies or being acquired. Due diligence, valuation, integration, and deal structure. Use when evaluating acquisitions, preparing for acquisition, M&A due diligence, integration planning, or deal negotiation.
create-plan
antinomyhq
Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.