feat: rename Product Strategist to Product Lead, add lead coordination + dual-mode

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-22 22:42:35 +03:00
parent 6430ab3eff
commit 27e03cc56c
20 changed files with 6305 additions and 14 deletions
@@ -0,0 +1,27 @@
+# Agent Pipeline — Mandatory
+
+## 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.
+
+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.
+
+## 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
+
+## Announcement Format
+
+Always start with a brief announcement before dispatching agents:
+
+> 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.
+
+## 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.