team-charters

What problem does it solve?

Provides role charters (mission, ownership, core principles, and quality bar) for a multi-agent coding team. Each charter defines the role's mission, ownership scope, core principle (boundary constraints), and quality bar. Most roles also include communication rules. Consumed by the coordinator during task decomposition to assign work to the correct role.

Core Features & Use Cases

• Defines missions, ownership scopes, core principles, quality bars, and communication rules for each role.
• Serves as a centralized reference to inform task decomposition and ownership decisions across architects, backend, frontend, and other roles.
• References/ references files provide role-specific charters (architect, backend, dba, devops, frontend, pm, security, teamlead, tester, ux).

Quick Start

Read a role's charter in references/<role>.md to understand its mission, ownership, and boundaries.