chore(agents): flatten delegation model to spec-and-review architecture#371
Merged
Conversation
Replace nested agent invocation (orchestrator → dev-team-lead → Haiku agents) with a flat model where the orchestrator launches all agents directly using specs produced by the dev-team-lead. The dev-team-lead now operates in three modes: - [MODE: spec] — reads wiki/codebase, returns structured implementation specs - [MODE: review] — reads modified files, returns VERDICT with fix specs - [MODE: commit] — stages, commits with trailers, pushes, creates PR, watches CI This eliminates the unreliable nested Agent tool calls that caused the dev-team-lead to write production code directly. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
|
🎉 This PR is included in version 1.10.0-beta.78 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Contributor
|
🎉 This PR is included in version 1.11.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
[MODE: spec](produces structured implementation specs),[MODE: review](reviews code, returns verdicts),[MODE: commit](commits, pushes, creates PR, watches CI)/develop,/epic-run,/epic-close) to use the multi-phase orchestration flow: spec → implement → review → commitMotivation
Nested Agent tool calls are unreliable — the dev-team-lead frequently falls back to writing production code directly, violating the delegation protocol. This restructuring eliminates nested delegation entirely.
Files Changed
.claude/agents/dev-team-lead.md— Major rewrite to three-mode protocol.claude/skills/develop/SKILL.md— Step 6 rewritten to multi-phase orchestration (6a-6h).claude/skills/epic-run/SKILL.md— Phase 2 steps 2.5-2.6, 2.9, 3.3 updated.claude/skills/epic-close/SKILL.md— Step 4 refinement PR updated.claude/agents/backend-developer.md— Minor wording update for orchestrator routing.claude/agents/frontend-developer.md— Minor wording update for orchestrator routingCLAUDE.md— Agent table, delegation enforcement, orchestrator delegation list updated.claude/agent-memory/dev-team-lead/MEMORY.md— Updated to reflect three-mode protocolTest plan
/developphases connect correctly (6a → 6b/6c → 6d → 6e → 6f → 6g → 6h)/developsession on a story to validate the new flow in practiceCo-Authored-By: Claude Opus 4.6 noreply@anthropic.com