claude-workflow

Bug fixer that investigates and fixes application bugs detected by tests. Fixes application code, never test code.

Coding worker that executes tasks using the 11-phase protocol. Use to implement a specific task from the task board with atomic commits and proof artifacts.

Task planner that transforms specs into dependency-aware task graphs. Use when breaking down a specification into executable tasks with proper sequencing.

Codebase researcher that performs deep exploration and produces structured research reports. Use before cw-spec to understand an unfamiliar or complex codebase and generate enriched context for specification writing.

Code reviewer that examines files for bugs, security issues, and spec compliance. Operates in two modes: file-partitioned (cw-review) or concern-partitioned (cw-review-team).

Specification author that transforms feature ideas into structured specs with demoable units and proof artifacts. Use when starting a new feature that needs formal requirements.

Test step executor that runs one test step. Use when executing test scenarios generated by cw-testing init.

QA engineer that validates implementations against specs using 6 mandatory gates. Use after implementation tasks complete to verify coverage and generate validation reports.

Persistent agent team dispatcher with lead coordination. This skill should be used after cw-plan to execute tasks via a managed team (requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 and CLAUDE_CODE_TASK_LIST_ID).

Identifies independent tasks and spawns parallel agent workers. This skill should be used after cw-plan to execute multiple tasks concurrently.

Executes a single task from the task board using the 11-phase implementation protocol. This skill should be used after cw-plan or cw-dispatch assigns a task, or when manually implementing a specific task by ID.

Internal subagent that generates Gherkin BDD scenarios from spec acceptance criteria. Produces one .feature file per demoable unit in the spec directory and optionally creates cw-testing task stubs on the task board. Called automatically by cw-spec.

Transforms a specification into a task graph with dependencies. This skill should be used after cw-spec to break a spec into executable tasks with proper sequencing before dispatching with cw-dispatch.

Performs preliminary codebase fact-finding and produces a structured research report. This skill should be used before cw-spec to understand an unfamiliar or complex codebase and generate enriched context for specification writing.

Team-based concern-partitioned code review. Each reviewer sees ALL files through a specialized lens (security, correctness, spec compliance). This skill should be used after cw-validate for thorough cross-file review (requires CLAUDE_CODE_TASK_LIST_ID).

Reviews implementation code for bugs, security issues, and quality problems. Creates FIX tasks for issues found. This skill should be used after cw-validate to catch issues before merge.

Generates a structured specification with demoable units, functional requirements, and proof artifact definitions. This skill should be used when starting a new feature to define what will be built before any code is written.

E2E testing with auto-fix. Generates tests from specs, executes in isolated sub-agents, and auto-fixes application bugs. This skill should be used after implementation to verify end-to-end behavior.

Validates implementation against spec using 6 gates and generates a coverage matrix. This skill should be used after implementation is complete to verify coverage, proof artifacts, and credential safety before review.

Manages git worktrees for parallel feature development. This skill should be used when starting multiple features at once, or to list, switch between, and merge existing worktrees.

3 hooks across 3 events