What is sub-agent-driven development?
One lead agent owns a slice of work and hands narrow, independent tasks to specialist agents.
The lead owns the outcome. Builders implement, checkers verify, and one integrator owns the final diff and commit history.
Each specialist works in its own Git worktree, a separate working directory on its own branch, so agents working at the same time do not overwrite each other.
The builder does not approve its own work. A separate checker tests the claim that the work is complete, and a person decides whether the result passes a human gate.
Lessons that use it
- 08One lead agent, and specialistsOne agent owns the slice. The others get narrow tasks.
The ruleGive every agent one task and one owner, and keep the one who built it away from the one who approves it.
- 20Nobody grades their own homeworkA builder's report that it is done is a claim. Someone else decides if it is true.
The ruleUse review that the builder does not control, and make it look at the running product.