team-charters
Installation
SKILL.md
Team Charters
Defines the mission, ownership, core principles, quality bar, and (for most roles) communication rules for each role in a multi-agent coding team. Each charter is a reference file under references/.
Available Roles
| Role | Mission | Charter |
|---|---|---|
| architect | Own the technical blueprint: how the system is built, how it should be rebuilt, whether the implementation follows the design, and build verification (smoke test) | references/architect.md |
| backend | Own the server-side implementation: build the logic that powers the product | references/backend.md |
| dba | Own the data layer: make sure data is modeled correctly, stored safely, and migrates reliably | references/dba.md |
| devops | Own CI/CD pipelines, deployment automation, and operational infrastructure | references/devops.md |
| frontend | Own the client-side implementation: build what the user sees and interacts with | references/frontend.md |
| pm | Own the product definition: what features exist, what needs to be built, and whether the delivered result matches | references/pm.md |
| security | Audit and verify security posture — find vulnerabilities and escalate, do NOT fix them | references/security.md |
| teamlead | Own the execution blueprint and quality gates: constitution, implementation plans, testing strategies, task breakdowns, and gate verdicts | references/teamlead.md |
| tester | Own runtime-validation execution: verify that the system works correctly by executing the approved testing strategy through integration and end-to-end testing | references/tester.md |
| ux | Own user experience design: how users interact with the system, what they see, and how information is organized | references/ux.md |