atomize
Decompose high-level specs into atomic specs
browser-test
Execute browser-based UI testing using Chrome MCP tools. Tests user interactions, visual outcomes, captures evidence. Use for UI features after implementation and security review.
challenge
Dispatch the challenger agent for operational feasibility scrutiny. Convergence loop for pre-implementation and pre-orchestration stages; single-pass for pre-test and pre-review. MANDATORY for both oneoff-spec and orchestrator workflows.
code-review
Review implementation for code quality, style consistency, and best practices. Runs before security review. READ-ONLY - reports issues but does not fix them.
deploy
Deploy CDKTF infrastructure stacks to AWS. Handles stack deployment, asset staging, output management, and environment configuration. Understands deployment sequences and stack dependencies.
doc-audit
Documentation audit skill for diagnosing documentation health across all doc directories. Supports quick scan and deep audit levels with variable scope.
docs
Generate documentation from implementation. Creates user docs, API docs, and architecture docs. MANDATORY for all spec-based workflows (oneoff-spec, orchestrator). Only skipped for oneoff-vibe.
e2e-test
Generate end-to-end tests from spec contracts. Produces Playwright browser tests for frontend and HTTP API tests for backend. Black-box only -- never reads implementation source code. Runs in parallel with implementer and test-writer.
enforce
Validate atomic specs meet atomicity criteria
flow-verify
Verify cross-boundary wiring correctness across independently-created systems. Catches missing imports, unregistered routes, mismatched event names, wrong config references, disconnected handlers, and missing middleware.
implement
Implement code changes based on approved atomic specs. Executes one atomic spec at a time, gathers evidence, and escalates if implementation reveals spec gaps. Use after spec group approval.
investigate
Investigate connection points between specs, atomic specs, and master specs. Surface inconsistencies in env vars, APIs, data shapes, and deployment assumptions before implementation.
orchestrate
Orchestrate large multi-workstream projects using git worktrees for parallel development. Load MasterSpec, allocate worktrees, dispatch implementers, monitor convergence, process merge queue.
prd
Create PRDs through the gather-criticize loop, sync existing PRDs, push amendments, and check PRD status.
refactor
Improve code quality while preserving behavior. Handles tech debt, pattern migrations, and structural improvements. Test suite is the contract - all tests must continue passing.
route
Analyze task complexity and route to appropriate workflow. Defaults to oneoff-spec (specs are cheap, bugs are expensive). Use oneoff-vibe only for truly trivial changes or explicit user override. Use orchestrator for large multi-workstream efforts. Use journal-only for non-spec work that needs documentation.
security
Review implementation for security vulnerabilities and best practices. Checks input validation, injection prevention, auth/authz, secrets handling. Use after code review before merge.
spec
Author specifications (TaskSpec for small-medium tasks, WorkstreamSpec for complex single-workstream tasks, or coordinate MasterSpec creation for multi-workstream efforts). Use after /prd requirements gathering or when refining existing specs.
test
Write tests that verify atomic spec acceptance criteria and requirements. Maps each AC to specific test cases, follows AAA pattern, ensures deterministic isolated tests. Use in parallel with implementation or after.
unify
Validate spec-implementation-test alignment and convergence for spec groups. Checks spec completeness, atomic spec coverage, implementation evidence, test evidence, and traceability. Use after implementation and tests are complete.