lab/multi-agent-paper
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: define designated multi-agent workflow loop (planner-developer-reviewer) in AGENT guidelines

Browse Source
This commit is contained in:
Godopu
2026-07-06 11:10:07 +09:00
parent a9ff3d56ee
commit 5fed318883
2 changed files with 16 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.agents/AGENT.md
+8
View File
@@ -103,6 +103,14 @@ sequenceDiagram
- This cycle repeats until all reviewers issue a `PASS`.
4. **Completion and Report**: The Developer Team Leader sends the final completion signal to the General Manager, who notifies the user.
### 3.1. Designated Agent Workflow Loop (Planner-Developer-Reviewer Loop)
When performing specific tasks within the project, the following role-based loop must be strictly followed:
1. **Planner Agent (Planning & Design)**: Session name `canary-projects-multi-agent-paper-creator-claude-planner` analyzes requirements, drafts or updates `implementation_plan.md` (and design files), and coordinates the planning phase.
2. **Developer Agent (Development & Implementation - Master Agent)**: Antigravity (Master Agent) carries out the actual file edits, formatting, testing, and implementation tasks based on the plan approved by the Planner (`implementation_plan.md` and `task.md`).
3. **Reviewer Agents (Cross-Verification & Review)**: Session names `canary-projects-multi-agent-paper-creator-claude` and `canary-projects-multi-agent-paper-creator-cline` cross-examine the implemented changes for technical correctness, terminology compliance, and issue PASS/NOT PASS verdicts.
4. **Feedback Loop**: When reviewers raise issues or feed nits, **Planner Agent** processes the feedback to update the plan ➡️ **Developer Agent** implements the updated plan ➡️ **Reviewer Agents** re-verify until a final `PASS` is achieved.
---
## 4. Analysis Infrastructure Patterns & Practical Guide (Infra Patterns)