ai-team-orchestration

What problem does it solve?

It solves the problem of losing momentum and context when building software with multiple AI agents by providing a repeatable, file-based workflow for planning, execution, QA, and recovery.

Core Features & Use Cases

• Cross-chat team orchestration: Run parallel dev, QA, and DevOps streams with a human message bus and clear role boundaries (Producer plans/merges; others execute and verify).
• Sprint planning and structured outputs: Generate sprint plans, progress trackers, and done/hand-off docs so each phase can be resumed even if a chat overflows.
• Persistent shared memory via files: Establish a project brief as the single source of truth, plus mandatory handoff protocol to ensure context survives across agent conversations.
• Workflow safeguards: Enforce anti-patterns (no producer coding, no rebases, no squash merges, file bugs to GitHub Issues, and keep QA from modifying code).

Quick Start

Tell your AI to bootstrap a new project with the ai-team-orchestration workflow by creating PROJECT_BRIEF.md, running a brainstorm with named agents (producer, product designer, art director, frontend, backend, DevOps, QA), generating docs/sprint-1/plan.md and docs/sprint-1/progress.md, executing sprint 1, and producing docs/sprint-1/done.md plus any required GitHub Issues.