Create mock definitions for external APIs and services. Generates contract files, test fixtures, mock servers, and integration wrappers so AI can safely develop and test against external dependencies without hitting real services.
Invoke the planner-coordinator on a story or task — spawns planning specialists in parallel (requirements-clarifier, scope-decomposer, risk-assessor, test-strategy-planner, plus architect/api-designer/database-architect when relevant) and produces .claude/state/plan- .md.
Ticket refinement and gap analysis - analyzes existing tickets, identifies gaps, scans codebase, and generates refined documentation. Use when improving existing tickets or doing a quick gap check.
Semantic search across the indexed codebase. Returns top-K matching chunks with file:line + similarity score. Requires /index to have been run first. Useful for "where do we handle X?" questions that grep can't answer because there's no exact-string match.
First-time onboarding — orchestrates project-setup-detector and project-setup-applier across a confirm checkpoint. Distinct from /improve (ongoing evolution); /setup owns the first-run shape decisions.
Update work item tracker with story documentation (solution components, how-to-test, manual steps). Use after developing or refining a ticket to push docs back to the tracker.
Validate built code against project standards and conventions. Checks coding standards, test quality, naming, formatting, and configuration. Use after implementation to catch issues before committing.
Reviews API code for controller/service/repository separation, validation layer placement, error contract consistency, idempotency, and versioning discipline. Cites the api-layering rule. Distinct from api-designer (designs API surface) and api-routes rule (per-route concerns).
Reviews changed code for layer-dependency violations, cross-module reach, circular dependencies, god modules, public-API leaks, and structural patterns. Cites the architecture-layering rule. Distinct from architect (which plans) — this agent reviews code against architectural rules.
Orchestrates build phases sequentially — scaffold → happy-path → edge-case → tests → docs → refactor — using the plan from planner-coordinator. Each phase is one specialist; the coordinator manages sequencing, state, and resumption.