add-tests
Generate tests for a completed phase based on UAT criteria and implementation
Add phase to end of current milestone in roadmap
How it fires
How this command gets triggered: by you, by Claude, or both.
/add-phaseContext preview
What this command does when you run it.
Add phase to end of current milestone in roadmap
name: gsd:add-phase description: Add phase to end of current milestone in roadmap argument-hint: <description> allowed-tools: - Read - Write - Bash
<objective> Add a new integer phase to the end of the current milestone in the roadmap.
Routes to the add-phase workflow which handles:
</objective>
<execution_context> @~/.claude/get-shit-done/workflows/add-phase.md </execution_context>
<context> Arguments: $ARGUMENTS (phase description)
Roadmap and state are resolved in-workflow via `init phase-op` and targeted tool calls. </context>
<process> **Follow the add-phase workflow** from `@~/.claude/get-shit-done/workflows/add-phase.md`.
The workflow handles all logic including: 1. Argument parsing and validation 2. Roadmap existence checking 3. Current milestone identification 4. Next phase number calculation (ignoring decimals) 5. Slug generation from description 6. Phase directory creation 7. Roadmap entry insertion 8. STATE.md updates </process>
GSD Pro — The most powerful AI coding workflow for Claude Code. Free alternative to Cursor Composer, Copilot Workspace, Devin & Bolt. Multi-model routing, rollback/recovery, adaptive context. Fork of 30K★ original. npx get-shit-done-cc
Repo: itsjwill/gsd-pro
Generate tests for a completed phase based on UAT criteria and implementation
Capture idea or task as todo from current conversation context
Audit milestone completion against original intent before archiving
Run all remaining phases autonomously — discuss→plan→execute per phase
List pending todos and select one to work on
Archive accumulated phase directories from completed milestones