spec-workflow

# Spec Workflow Spec-driven development transforms feature requests into structured specs through sequential phases, then executes them task-by-task. ## Decision Tree: Where to Start | Situation | Command | |-----------|---------| | New feature, want guidance | `/ralph-specum:start <name> <goal>` | | New feature, skip interviews | `/ralph-specum:start <name> <goal> --quick` | | Large feature needing decomposition | `/ralph-specum:triage <goal>` | | Resume existing spec | `/ralph-specum:start` (auto-detects) | | Jump to specific phase | `/ralph-specum:<phase>` | ## Single Spec Flow ``` start/new -> research -> requirements -> design -> tasks -> implement ^ optional prototype overlay, then return ``` Each phase produces a markdown artifact under the resolved `<basePath>/`. Normal mode pauses for approval between phases. Quick mode runs all phases then auto-starts execution. Prototype is an optional overlay, not a main phase. The main `phase` remains `research`, `requirements`, `design`, `tasks`, or `execution`; live prototype work is stored in `activePrototypes`. Resolve the configured spec root and `basePath` before any overlay operation. Follow [`references/phase-transitions.md`](references/phase-transitions.md) when suggesting, starting, resuming, cancelling, or consuming prototype evidence. ### Phase Commands | Command | Agent | Output | Purpose | |---------|-------|--------|---------| | `/ralph-specum:research` | r...