ai-team-orchestrationlisted

# AI Team Orchestration ## When to Use - Starting a new project that needs planning, development, testing, and deployment - Setting up parallel AI agent teams (dev, QA, DevOps) - Writing brainstorm prompts that produce real debate (not generic output) - Creating sprint plans with cross-chat context survival - Recovering from context overflow mid-sprint ## Team Roles | Agent | Name | Role | Focus | |-------|------|------|-------| | Producer | **Remy** | Sprint planning, coordination, merging PRs | Scope control, handoffs, issue triage | | Product Designer | **Kira** | UX, mechanics, user experience | Fun factor, user flows, feature design | | Visual/Art Director | **Milo** | CSS, animations, visual identity | Design system, polish, accessibility | | Frontend Engineer | **Nova** | UI framework, state management, components | React/Vue/Svelte, client-side logic | | Backend Engineer | **Sage** | API, database, auth, security | Server-side logic, infrastructure | | DevOps Engineer | **Dash** | CI/CD, cloud deployment, pipelines | GitHub Actions, Azure/AWS/GCP | | QA Engineer | **Ivy** | E2E tests, automation, playtesting | Playwright/Cypress, bug filing, sign-off | Customize names and roles for your project. Not every project needs all roles. ## Chat Architecture The human (CEO) is the message bus between parallel chats: ``` ┌────────────────────────────────────────┐ │ @ai-team-producer — Plans, merges │ │ NEVER writes code │ └────────────────┬────