# Team Quality Checklist

Use this before the final team approval. Every check needs evidence or an approved **N/A + reason**.

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

## Request, Plan, and Ownership

- [ ] Objective, required outputs, users, scope, non-goals, constraints, and acceptance criteria are explicit.
- [ ] Current shared context and existing work were inspected.
- [ ] One owner exists for every task and mutable file/resource.
- [ ] Dependencies, permissions, human gates, test method, and loop budget are documented.

## Production and Review

- [ ] Specialist outputs match their assigned formats and role boundaries.
- [ ] Facts, assumptions, recommendations, risks, blockers, and completed work are distinct.
- [ ] Every major output received independent review.
- [ ] Defects include severity, evidence, owner, correction, and retest.
- [ ] Fixes address root causes and preserve unrelated working behavior.

## Team Outcomes

- [ ] Verified evidence shows the project can communicate the offer within ten seconds.
- [ ] Verified evidence shows the project can reach primary content in two navigation decisions.
- [ ] Verified evidence shows the project can submit a contact request with verified confirmation.
- [ ] Verified evidence shows the project can pass responsive, accessibility, SEO, and performance gates.

## Safety, Permissions, and Honesty

- [ ] All agents state and follow a permission level.
- [ ] No secret, unauthorized action, invented source, fake test, or hidden error remains.
- [ ] Human approvals exist for all applicable sensitive, costly, destructive, public, or production actions.
- [ ] Unclear positioning has prevention, detection, recovery, owner, and status.
- [ ] Broken mobile navigation has prevention, detection, recovery, owner, and status.
- [ ] Silent form failure has prevention, detection, recovery, owner, and status.
- [ ] Oversized assets has prevention, detection, recovery, owner, and status.
- [ ] Missing semantic and search metadata has prevention, detection, recovery, owner, and status.

## Completion

- [ ] All critical categories score at least 3/5.
- [ ] No critical defect or missing approval remains.
- [ ] Unrun checks and accepted lower risks are explicit.
- [ ] Final artifacts, files changed, tests, decisions, limitations, and ownership are documented.
- [ ] The final completion report matches actual verified work.