From d12e98bec14615398dc5ff4cc26b822e52acd243 Mon Sep 17 00:00:00 2001 From: Daniil Date: Sun, 22 Mar 2026 22:57:47 +0300 Subject: [PATCH] feat: update agent-pipeline rule for hierarchical dispatch model Co-Authored-By: Claude Opus 4.6 (1M context) --- .claude/rules/agent-pipeline.md | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-) diff --git a/.claude/rules/agent-pipeline.md b/.claude/rules/agent-pipeline.md index 775ec41..1f1fb7f 100644 --- a/.claude/rules/agent-pipeline.md +++ b/.claude/rules/agent-pipeline.md @@ -2,26 +2,25 @@ ## The Rule -This project has a 16-agent specialist team (`.claude/agents/`). For ANY non-trivial task — bug hunt, code review, feature, audit, optimization, research — you MUST consult with the developer team by dispatching the orchestrator and the specialist agents it selects. +This project has a 20-agent team organized in a 4-tier hierarchy (`.claude/agents/`). For ANY non-trivial task — bug hunt, code review, feature, audit, optimization, research — you MUST consult with the developer team by dispatching the orchestrator. -Built-in agents (e.g. `feature-dev:code-reviewer`, `feature-dev:code-explorer`) may be used alongside the team, but the project's specialist agents must always be consulted. +The orchestrator handles everything: it dispatches leads (Architecture Lead, Quality Lead, Product Lead), who in turn dispatch their specialists. Results bubble up with structured audit trails. ## Pipeline 1. **Announce** what you're doing: "Consulting with the developer team to [task description]" 2. **Dispatch the orchestrator** agent with your analysis of the task -3. **Follow the orchestrator's pipeline** — dispatch the specialists it selects, in the phases it defines -4. Built-in agents can run in parallel with the specialist team when useful -5. **Report results** — synthesize all outputs into a coherent response, crediting which specialists contributed +3. **Receive results** — the orchestrator returns a synthesized recommendation with a full audit trail of all agent calls +4. **Report results** — present the synthesis to the user, crediting which specialists contributed + +You do NOT need to: dispatch individual agents, process handoffs, manage chain depth, or sequence phases. The orchestrator → lead → specialist hierarchy handles all of this internally. ## Announcement Format -Always start with a brief announcement before dispatching agents: +Always start with a brief announcement before dispatching the orchestrator: -> Consulting with the developer team: dispatching [Agent 1], [Agent 2], [Agent 3] to [task summary]. - -This tells the user which specialists are working and on what. +> Consulting with the developer team: dispatching orchestrator to [task summary]. ## Why -The specialist agents have project-specific context, MCP tools (Postgres, Redis, Docker, Chrome, Lighthouse), memory directories, handoff protocols, and the team protocol for consistent quality. Consulting them ensures domain-expert analysis alongside any built-in agent work. +The hierarchical agent system provides: autonomous agent-to-agent collaboration, structured guardrails (depth limits, loop prevention, cost control), full audit trails, and domain-expert analysis at every level. The orchestrator selects the right leads, leads select the right specialists, and each agent can consult others directly when needed.