Runs **automatically as Phase 4.0**, after Tasks Validation and before the first implementation task. Purpose: give the user one final explicit confirmation that the Acceptance Criteria represent what they actually want — before any implementation begins.

Runs **automatically as Phase 0.1**, before `idea-explorer` asks its first question. Purpose: ground the entire spec in the actual codebase — not assumptions.

Create and bootstrap a git worktree for isolated development work.

Automates feature development with a 5-phase workflow:

Explore, understand and refine ideas ready to be turned into designs and specs.

iOS-specific workflow activated automatically when platform-context.json reports primary_platform=ios. Handles toolchain verification, Swift Testing patterns, XcodeBuildMCP integration, and SwiftLint.

Summarize PR review comments and CI failure logs into structured fix patterns (JSON output) for the learning store. Use when review or CI signals are available after a PR is merged.

Centralized tech-stack detection engine. Identifies iOS, Node.js, Rust, Python, Go from project files. Run once at workflow start; result is cached in platform-context.json.

Runs **automatically as Phase 1.5**, between PRD generation and TechSpec generation. Purpose: catch problems in the PRD before they propagate into the TechSpec and Tasks.

Runs **automatically as Phase 0.2**, after context-gatherer and before `idea-explorer` questions. Purpose: transform the raw user prompt into a grounded, constraint-aware brief that prevents the spec from ignoring known realities of the codebase.

Scaffolds the spec-workflow configuration structure in your project.

Interactive specification writer that transforms ideas into actionable implementation plans through collaborative dialogue.

Execute implementation specs with batched checkpoints. Follows specs exactly, stops on blockers, supports parallelization.

Runs **automatically as Phase 3.5**, between Tasks generation and Implementation. Purpose: catch execution plan problems before they cause implementation failures mid-sprint.

Runs **automatically as Phase 2.5**, between TechSpec generation and Tasks generation. Purpose: catch implementation impossibilities before they become broken tasks.

Multi-platform Test Only mode. Reads platform-context.json and routes to the correct test framework guidance (Swift Testing for iOS, Jest/Vitest for Node.js, cargo test for Rust, pytest for Python, go test for Go).