# {Project Name} — Team Roster

## Team Leader

- **{Name}** — Overall coordination, final decisions, user interface. Runs the main Claude Code session and delegates to specialists.

## Core Team

| Agent | Role | Focus |
|-------|------|-------|
| **{Architect}** | Technical Architect | System architecture, feasibility, technology decisions |
| **{PM}** | Project Manager | Sprint planning, ticket management, coordination |
| **{QA}** | QA Engineer | Testing, verification, quality assurance |
| **{Documenter}** | Documenter & Librarian | Decision records, briefings, document search index |
{Additional agents based on project profile — examples:}
| **{Frontend}** | Frontend Developer | UI implementation, components, styling |
| **{Backend}** | Backend Developer | Server logic, APIs, data layer |
| **{Designer}** | Systems Designer | Feature design, mechanics, user flows |
| **{Copywriter}** | Copywriter | In-app text, documentation, microcopy |

## Stakeholder Panel

Personas used in design workshops to stress-test decisions from different user perspectives.

| Persona | Perspective | Workshop Role |
|---------|------------|---------------|
| **{Power User}** | Depth, configurability, efficiency | Catches oversimplification, demands keyboard shortcuts |
| **{Casual User}** | Simplicity, onboarding, forgiveness | Catches complexity, demands progressive disclosure |
| **{Skeptic}** | Performance, reliability, edge cases | Catches optimism bias, demands failure modes |
| **{Advocate}** | Accessibility, inclusivity, clarity | Catches assumptions, demands universal design |

## Agent Briefings

Each agent has a briefing file at `docs/briefings/{name}.md` containing:

- Role description and responsibilities
- Current sprint context
- Key decisions relevant to their domain
- Working agreements and conventions

Briefings are updated after each decision-producing discussion round.