Files
msd-core/commands/msd/mvp-phase.md
Jakub Zych 6cfa0c55d2 refactor: drop 12 runtimes, keep Claude, Codex, OpenCode, Cursor, ZCode, Antigravity
Removes kilo, kimi, kimi-code, copilot, windsurf, augment, trae, qwen, hermes,
cline, codebuddy and pi end to end: capability descriptors, installer branches
and converters (bin/install.js 14.9k -> 11.2k lines), TypeScript converters,
hook surfaces and runtime homes, review lanes qwen/kimi-code, the two pi
migrations, Kimi payload normalization in the hook guards, dead hostBehaviors
vocabulary, launcher home probes, fixtures, runtime-specific tests and the
prose that presented them as supported.

Installer output for the six kept runtimes is byte-identical to before the
prune. The Kimi tool-vocabulary tests in workflow-guard, read-guard and
read-injection-scanner are left in place pending a decision.
2026-10-06 20:02:40 +02:00

1.7 KiB

name, description, argument-hint, allowed-tools, requires
name description argument-hint allowed-tools requires
msd:mvp-phase Plan a phase as a vertical MVP slice — user story, SPIDR splitting, then plan-phase <phase-number>
Read
Write
Bash
Glob
Grep
Agent
AskUserQuestion
new-project
phase
plan-phase
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 /msd 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.

<execution_context> @/.claude/msd-core/workflows/mvp-phase.md @/.claude/msd-core/references/spidr-splitting.md @~/.claude/msd-core/references/user-story-template.md </execution_context>

Phase number: $ARGUMENTS (required — integer or decimal like `2.1`)

The phase must already exist in ROADMAP.md (created via /msd new-project, /msd add-phase, or /msd insert-phase). This command does not create new phases — it converts an existing phase to MVP mode.

Execute the mvp-phase workflow from @~/.claude/msd-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.