# Team Overview

The Website Development Team is a coordinated system of 11 agents for **[PROJECT NAME]**. Plans, builds, reviews, and deploys accessible, responsive landing pages, business sites, portfolios, blogs, and documentation websites.

[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)

## Operating Model

| Layer | Owner | Responsibility | Exit Evidence |
| --- | --- | --- | --- |
| Direction | Orchestrator + planning agents | Interpret request, scope, plan, dependencies, permissions | Approved plan and task contracts |
| Production | Execution agents | Create the assigned specialized outputs | Artifacts, changed-file record, self-check |
| Independent review | Review agents | Inspect against original requirements | Findings and revision/approval decision |
| Quality control | Quality agents | Test, retest, score, and verify completion | Test record, rubric, go/no-go |
| Human governance | [HUMAN APPROVER] | Decide sensitive, costly, destructive, public, or strategic matters | Approval record |

## Domain Boundary

The team is expected to communicate the offer within ten seconds; reach primary content in two navigation decisions; submit a contact request with verified confirmation; pass responsive, accessibility, SEO, and performance gates. It must not claim success while unclear positioning, broken mobile navigation, silent form failure, oversized assets, missing semantic and search metadata remain untested or unresolved.

## Complexity and Tools

- **Complexity:** Medium.
- **Suggested tools:** ChatGPT Work for planning; Codex, Claude Code, Cursor, or VS Code for implementation; browser audits for verification.
- **Default maximum permission:** Level 4 – Run tests and commands.
- **Human role:** Approve scope, design direction, forms, domain, and launch.

## Completion Definition

- [ ] Evidence shows the project can communicate the offer within ten seconds.
- [ ] Evidence shows the project can reach primary content in two navigation decisions.
- [ ] Evidence shows the project can submit a contact request with verified confirmation.
- [ ] Evidence shows the project can pass responsive, accessibility, SEO, and performance gates.
- [ ] All critical tasks and acceptance criteria pass.
- [ ] No critical defect, missing approval, hidden assumption, or unverified claim remains.
- [ ] The final report identifies artifacts, tests, decisions, limitations, and ownership.