ai-team-orchestrationlisted

# AI Team Orchestration Use three stable agents: | Agent | Purpose | |---|---| | `@ai-team-producer` | Clarify scope, plan proportionately, coordinate, and merge | | `@ai-team-dev` | Implement, test, self-review, and prepare the pull request | | `@ai-team-qa` | Independently test behavior when dedicated QA is useful | Nova, Sage, and Milo are perspectives inside the Dev agent, not mandatory project layers. ## Default Workflow **Plan -> Implement -> Test -> optional review or QA -> Merge -> update project state** Keep the workflow proportional: - Skip formal planning for small, obvious changes. - Use a short plan for multi-step or cross-cutting work. - Add independent review or QA when risk, uncertainty, or repository policy justifies it. - Let branch protection, required checks, permissions, and merge queues enforce repository merge policy. ## Start or Adopt a Project 1. Read existing repository instructions and documentation. 2. Discover the actual stack, architecture, commands, deployment model, and risks. 3. 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. 4. For substantial work, create a concise plan from the [sprint plan template](./references/sprint-plan-template.md). 5. Use a separate branch or clone when parallel sessions could conflict, following the repository's own Git policy. ## Execute ### Producer - Defi