ai-team-orchestration

1# AI Team Orchestration
2 
3Use three stable agents:
4 
5| Agent | Purpose |
6|---|---|
7| `@ai-team-producer` | Clarify scope, plan proportionately, coordinate, and merge |
8| `@ai-team-dev` | Implement, test, self-review, and prepare the pull request |
9| `@ai-team-qa` | Independently test behavior when dedicated QA is useful |
10 
11Nova, Sage, and Milo are perspectives inside the Dev agent, not mandatory project layers.
12 
13## Default Workflow
14 
15**Plan -> Implement -> Test -> optional review or QA -> Merge -> update project state**
16 
17Keep the workflow proportional:
18 
19- Skip formal planning for small, obvious changes.
20- Use a short plan for multi-step or cross-cutting work.
21- Add independent review or QA when risk, uncertainty, or repository policy justifies it.
22- Let branch protection, required checks, permissions, and merge queues enforce repository merge policy.
23 
24## Start or Adopt a Project
25 
261. Read existing repository instructions and documentation.
272. Discover the actual stack, architecture, commands, deployment model, and risks.
283. Create or update `PROJECT_BRIEF.md` only when durable cross-session context is useful. Start from the [project brief template](./references/project-brief-template.md) and omit irrelevant sections.
294. For substantial work, create a concise plan from the [sprint plan template](./references/sprint-plan-template.md).
305. Use a separate branch or clone when parallel sessions could conflict, following the repository's own Git policy.
31 
32## Execute
33 
34### Producer
35…