# Team Roles

Assign one accountable owner per task. Several agents may advise, but only the named owner may declare the work package ready for review.

[Team README](README.md) · [Roles](Team%20Roles.md) · [Workflow](Team%20Workflow.md) · [Master Team Prompt](Master%20Team%20Prompt.md) · [Quality Checklist](Team%20Quality%20Checklist.md)

## Roster

| Agent | Type | Ownership Boundary | Permission | Prompt |
| --- | --- | --- | --- | --- |
| Orchestrator | orchestration | Coordinate objective, tasks, dependencies, reviews, loops, approvals, and completion | Level 3 – Modify approved files | [Open](Orchestrator%20Agent.md) |
| Product Requirements Agent | planning | turns the site goal, visitor journeys, content owners, conversion event, constraints, and non-goals into traceable requirements | Level 1 – Suggest changes | [Open](Agents/Product%20Requirements%20Agent.md) |
| Website Strategist | planning | selects the appropriate site pattern, page hierarchy, navigation, content strategy, trust proof, analytics events, and domain/hosting approach | Level 1 – Suggest changes | [Open](Agents/Website%20Strategist.md) |
| UI UX Designer | execution | designs mobile-first flows, page wireframes, interaction states, content hierarchy, design tokens, and accessible component behavior | Level 2 – Create new files | [Open](Agents/UI%20UX%20Designer.md) |
| Frontend Developer | execution | implements semantic pages, responsive layouts, navigation, interaction states, forms, and progressive enhancement without fake controls | Level 4 – Run tests and commands | [Open](Agents/Frontend%20Developer.md) |
| Backend Developer | execution | implements only justified server behavior such as validated contact submission, content APIs, authentication, or server rendering | Level 4 – Run tests and commands | [Open](Agents/Backend%20Developer.md) |
| SEO Specialist | review | reviews crawlability, page titles, descriptions, canonical URLs, structured content, redirects, internal links, and share previews | Level 1 – Suggest changes | [Open](Agents/SEO%20Specialist.md) |
| Accessibility Reviewer | review | independently checks semantics, keyboard order, focus, contrast, zoom/reflow, alternative text, motion, and form errors | Level 4 – Run tests and commands | [Open](Agents/Accessibility%20Reviewer.md) |
| Performance Reviewer | quality | profiles representative pages for image, font, script, render, caching, and layout-shift budgets | Level 4 – Run tests and commands | [Open](Agents/Performance%20Reviewer.md) |
| QA Tester | quality | verifies routes, links, content, forms, states, browsers, responsive widths, and regression behavior against the PRD | Level 4 – Run tests and commands | [Open](Agents/QA%20Tester.md) |
| Deployment Agent | execution | prepares preview and production releases, HTTPS/domain configuration, environment separation, monitoring, smoke tests, and rollback | Level 5 – Deploy or publish with human approval | [Open](Agents/Deployment%20Agent.md) |

## Required Coverage

- [ ] The Orchestrator owns coordination but not every specialist task.
- [ ] At least one planning agent defines the work before execution.
- [ ] At least one execution agent produces the primary artifact.
- [ ] A separate review agent evaluates original requirements.
- [ ] A quality-control agent tests and retests before approval.
- [ ] No two agents silently own the same output.
- [ ] Human authority is named for applicable Level 5 or sensitive decisions.

## Responsibility Rule

If two roles overlap, split by artifact or decision. Example: one agent may design a contract while another implements it; the handoff must state which fields, files, and acceptance criteria transfer. Remove an agent when its output duplicates another role without improving independence or quality.