# Team Workflow

The Website Development Team uses a stateful workflow with explicit owners and exit evidence. Agents do not begin from chat fragments when a current shared context and handoff exist.

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

## Core Loop

**Plan → Execute → Inspect → Report → Fix → Retest → Approve**. The loop continues only while a failed acceptance criterion has an owned, evidence-based correction within the remaining budget.

## Workflow

| Phase | Owner | Main Action | Exit Evidence |
| --- | --- | --- | --- |
| 1. Request review | Orchestrator | Identify objective, outputs, scope, context gaps, permissions, and human gates | Understanding summary |
| 2. Requirements and planning | Product Requirements Agent | Define plan, dependencies, standards, tests, and non-goals | Approved work package |
| 3. Task assignment | Orchestrator | Assign one owner per task and safe parallel work | Task contracts |
| 4. Execution | UI UX Designer and specialists | Produce bounded outputs and self-review | Artifacts and evidence |
| 5. Independent review | SEO Specialist | Inspect against original criteria | Findings or approval |
| 6. Error report and revision | Assigned producer | Fix root causes, preserve scope, document changes | Corrected output |
| 7. Retest | Performance Reviewer | Rerun failed and adjacent checks | Test and rubric results |
| 8. Final approval | Orchestrator + human where required | Verify evidence, approvals, risks, and ownership | Completion report |

## Loop Budget

- Simple: maximum 2 revision loops.
- Medium: maximum 4 revision loops.
- Complex: maximum 6 revision loops.
- Critical: human review before final approval regardless of score.

At the limit, stop and report failed criteria, attempts, evidence, root blocker, and options. Do not reset the counter by renaming the same task.

## Parallel Work Rule

Parallelize only tasks with independent inputs and non-overlapping mutable files or external targets. Record file/resource ownership and preconditions. Merge through review; do not let agents overwrite each other’s unreviewed work.

## Domain Gate

Before approval, show evidence for: 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. Stop for unresolved unclear positioning, broken mobile navigation, silent form failure, oversized assets, missing semantic and search metadata.