Autonomous Claude Agent Team

autonomous-claude-agent-team
This is a specific, working example — not a flexible framework. It is a Claude Code plugin that implements one concrete workflow for building features with a team of AI agents. This is an example to show how you can build your own hook-driven workflow-as-code.

A hook-driven state machine for orchestrating three Claude Code agents — a lead, a developer, and a reviewer — through a structured feature development cycle.

What it is

Three agents work through a fixed cycle:

- Lead coordinates. Never writes or reviews code. Can only stop in BLOCKED or COMPLETE.
- Developer implements via TDD, runs strict lint, and signals done by writing to a state file. Cannot go idle without signalling.
- Reviewer runs git diff on uncommitted changes, runs typecheck/build/tests/lint, and returns APPROVED or REJECTED.

Every session is tracked by a GitHub issue. The PR is always created as a draft — this workflow never opens it. CodeRabbit reviews before humans do.

Hooks enforce the rules mechanically. The lead can't skip states, the developer can't commit before review, and no agent can stop at the wrong moment. This matters because LLMs are unreliable self-enforcers — hooks are code and can't be argued with.

How it works

RESPAWN happens at the start of every iteration. It shuts down the existing developer and reviewer and spawns fresh agents with only the plan and iteration context. This clears their context windows deliberately — accumulated noise from earlier iterations pollutes decisions in later ones.

State file at /tmp/feature-team-state-${CLAUDE_SESSION_ID}.json is the source of truth:

/autonomous-claude-agent-team:workflow transition  is the only way the lead changes state. Each state's transitions and guards are defined in…