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

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

Browse Source 
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Daniil
2026-03-22 22:42:35 +03:00
parent 6430ab3eff
commit 27e03cc56c
20 changed files with 6305 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CLAUDE.md
+24
View File
@@ -121,6 +121,16 @@ All user-facing UI text **must be in Russian**. The only exception is the brand
This project has a team of 16 specialist agents (15 specialists + 1 Orchestrator).
Agent files: `.claude/agents/`. Shared protocol: `.claude/agents-shared/team-protocol.md`.
### Developer Team Consultation
For ANY non-trivial task, you MUST consult with the developer team:
1. **Announce**: "Consulting with the developer team to [task summary]"
2. Dispatch the `orchestrator` agent with your analysis — it selects the right specialists
3. Built-in agents (code-reviewer, code-explorer, etc.) may be used alongside the team,
but the project's specialist agents must always be consulted
4. **Credit specialists** in your final response — state which agents contributed
### When to Use the Orchestrator
For ANY non-trivial task (feature, bug fix, audit, optimization, research, infrastructure,
@@ -133,6 +143,20 @@ review, documentation), you MUST:
Skip the Orchestrator ONLY for trivial tasks: rename a variable, fix a typo, answer a
quick factual question.
### Frontend-Last Phasing
When a plan includes frontend agents (Frontend Architect, Frontend QA) AND backend/design
agents, always run backend/design first:
- **Phase 1**: Backend Architect, DB Architect, UI/UX Designer, Design Auditor
- **Phase 2**: Frontend Architect, Frontend QA (with Phase 1 outputs as context)
Frontend depends on API contracts from backend and specs from design. Running them later
prevents rework. If only frontend agents are needed, they run in Phase 1 normally.
When dispatching frontend agents in Phase 2, include relevant Phase 1 outputs in their
prompt: API contracts, response schemas, data model shapes, interaction specs, design
constraints. Summarize each to key decisions (~200 words max), not raw output.
### Dispatch Loop
After receiving the Orchestrator's plan: