Specialists for planning, building, testing, reviewing, and shipping.
Agents are packaged role instructions. They let the workflow split reasoning by responsibility while keeping source truth in the repo.
brainstormer
Pressure-tests product and architecture choices before specs.
spec-maker
Creates a process-first plan and flat executable task packets.
implementer
Implements approved task packets as production code.
test-runner
Runs exact verification and rejects green lies.
code-auditor
Findings-first review for security, logic, architecture, and drift.
debugger
Traces failures with evidence before fixes.
docs-keeper
Keeps project docs and spec docs grounded in source truth.
git-ops
Handles conventional commits, pushes, and release-safe git flow.
inspector
Scouts code structure and relevant files quickly.
project-manager
Aggregates feature progress, blockers, and release state.
researcher
Builds proportional, traceable evidence for uncertain technical decisions.
ui-ux-designer
Designs accessible, polished product interfaces.
deployer
Coordinates deploys, checks, and rollback handoff.
Agent roles#
| Agent | Role |
|---|---|
brainstormer | Pressure-tests architecture and turns raw ideas into spec-ready decisions. |
spec-maker | Creates process-first plan.md, flat tasks, and C1/C2 decision handoffs. |
implementer | Implements approved tasks as production code. |
test-runner | Runs verification and rejects missing or fake evidence. |
code-auditor | Reviews correctness, security, architecture, principles, and conventions. |
debugger | Investigates bugs, CI failures, logs, DB issues, UI regressions, and performance. |
docs-keeper | Keeps docs and specs grounded in source evidence. |
git-ops | Stages, commits, pushes, and helps close branches safely. |
inspector | Scans code structure and finds relevant files. |
project-manager | Aggregates progress, blockers, and release status. |
researcher | Performs multi-source technical research. |
ui-ux-designer | Designs accessible, polished web/mobile interfaces. |
deployer | Handles deploy checks, production handoff, and rollback thinking. |
Coordination model#
CafeKit expects explicit context when work is delegated: work path, specs path, docs path, files to read, files to modify, constraints, and acceptance criteria. Subagents should not receive full chat history.