- name
- ai-team-orchestration
- description
- Bootstrap and run a lightweight multi-agent development team. Use when starting or adopting a project, planning work, coordinating implementation and optional QA, brainstorming with distinct perspectives, or preserving context across sessions.
AI Team Orchestration
Use three stable agents:
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
- Read existing repository instructions and documentation.
- Discover the actual stack, architecture, commands, deployment model, and risks.
- Create or update
PROJECT_BRIEF.mdonly when durable cross-session context is useful. Start from the project brief template and omit irrelevant sections. - For substantial work, create a concise plan from the sprint plan template.
- Use a separate branch or clone when parallel sessions could conflict, following the repository's own Git policy.
Execute
Producer
- Define the outcome, constraints, acceptance criteria, and explicit exclusions.
- Choose review and QA based on risk rather than ceremony.