faglo/remotion_service
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: update agent-pipeline rule for hierarchical dispatch model

Browse Source 
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Daniil
2026-03-22 22:57:47 +03:00
parent 063b460477
commit d12e98bec1
1 changed files with 9 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.claude/rules/agent-pipeline.md
+9 -10
View File
@@ -2,26 +2,25 @@
## The Rule ## 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 ## Pipeline
1. **Announce** what you're doing: "Consulting with the developer team to [task description]" 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 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 3. **Receive results** — the orchestrator returns a synthesized recommendation with a full audit trail of all agent calls
4. Built-in agents can run in parallel with the specialist team when useful 4. **Report results** — present the synthesis to the user, crediting which specialists contributed
5. **Report results** — synthesize all outputs into a coherent response, 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 ## 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]. > Consulting with the developer team: dispatching orchestrator to [task summary].
This tells the user which specialists are working and on what.
## Why ## 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.