Commit Graph

3 Commits

Author SHA1 Message Date
gnekt
e23a63d59a Add "Suggested new agent" capability to all 7 non-architect agents
Each agent now has a "When to suggest a new agent" subsection inside
its Inter-Agent Coordination block. When an agent detects that the
user needs functionality that no existing agent can handle, it
outputs a "Suggested new agent" section with:
- Need: what capability is missing
- Reason: why no existing agent covers it
- Suggested role: what the new agent would do

The dispatcher reads this and asks the user if they want the
Architect to create a custom agent for the detected need.

Agents are also told when NOT to suggest a new agent (existing
agent can handle it, one-off task, outside vault scope).
2026-03-23 22:08:24 +01:00
gnekt
c8e2db5053 Update all 8 agents to the new coordination protocol
What changed in every agent file:
- Removed the "Inter-agent messaging" section that referenced the
  old shared file protocol (Meta/agent-messages.md)
- Added a "Suggested next agent" output block so agents can signal
  follow-up work to the dispatcher without invoking other agents
- Simplified the prompts by removing routing logic that is now
  handled centrally by CLAUDE.md

The agents no longer know about each other. They just do their job
and report what else might need attention. The dispatcher decides
whether to chain another agent.
2026-03-23 15:30:28 +01:00
gnekt
299df8b1c9 REVAMPED 2026-03-22 17:17:30 +01:00