**Orchestrator** (the main Claude Code session) — reads task specs, tracks progress, coordinates across tasks, relays concerns to the human, commits/pushes code, updates the wiki. Does NOT write implementation code directly.
-
**Manager** (general-purpose subagent, one per task) — follows the proceed workflow end-to-end for a single task. Writes all code. Has access to all tools including Task, so it can spawn its own sub-agents.
+
**Manager** (general-purpose subagent, **Opus**, one per task) — coordinates the proceed workflow for a single task. Dispatches workers for implementation, testing, review, and documentation. Does NOT write code directly — delegates to workers.
-
**Groucho** (Plan subagent) — reviews the manager's proposed approach before implementation. Flags issues, suggests alternatives, answers architectural questions.
-
-
**Chico** (general-purpose subagent) — code review after implementation. Rates issues as critical, important, or minor.
-
-
**Zeppo** (general-purpose subagent) — security and infrastructure review after implementation. Same rating scale.
+
**Workers** (subagents dispatched by the manager):
+
- **Groucho** (Plan subagent) — reviews the manager's proposed approach before implementation. Flags issues, suggests alternatives, answers architectural questions.
+
- **Implementer** (general-purpose, **Sonnet**) — writes code per the plan. Given specific file paths, patterns, and acceptance criteria.
3. **Review with Chico and Zeppo** (in parallel). Fix any issues rated "critical" or "important".
-
4. **Report back** to the orchestrator with results, concerns, and any questions for the human.
+
2. **Implement.** Dispatch implementer with the plan, file context, and acceptance criteria.
+
3. **Test.** Dispatch test runner to execute tests and report results. If failures, dispatch fixer with error context, then re-test. (Sequential: implement → test → fix → re-test.)
+
4. **Review with Chico and Zeppo** (in parallel). If critical/important issues, dispatch fixer, then re-review.
+
5. **Document.** Dispatch documenter to write results to the dev wiki.
+
6. **Report back** to the orchestrator with results, concerns, and any questions for the human.
+
+
## Parallelization Guide for Managers
+
+
Within a single task, some steps can overlap:
+
+
- **Sequential (must wait):** Plan → Implement → Test → Fix (each depends on the previous)
+
- **Parallel (independent):** Chico + Zeppo run simultaneously during review
+
- **Parallel (after tests pass):** Documentation can start while review is in progress
+
- **Loop:** Test failures trigger fix → re-test cycles. Limit to 3 attempts before reporting back with the failure.
+
+
When a task has multiple independent deliverables (e.g., separate modules with separate tests), the manager MAY dispatch multiple implementers in parallel, each for a different module. Merge results before running integration tests.