# Feedback Loop

The Website Development Team uses feedback to correct a specific gap, not to restart the whole project or add unvalidated scope.

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

## Loop

**Plan → Execute → Inspect → Report → Fix → Retest → Approve**

| Step | Owner | Required Record | Exit Rule |
| --- | --- | --- | --- |
| Plan | Planning agent | Task contract and test method | Scope and dependencies clear |
| Execute | Assigned producer | Artifact and self-review | Output ready for inspection |
| Inspect | Independent reviewer | Evidence-based findings | Every issue classified |
| Report | Reviewer | Defect/revision handoff | Owner and criteria assigned |
| Fix | Producer | Narrow correction and change note | Root cause addressed |
| Retest | Quality agent | Original + adjacent test results | Failed criteria pass |
| Approve | Orchestrator/human | Decision and residual risks | Completion rule met |

## Revision Request

~~~markdown
# Revision Request
Defect/criterion: [ID]
Severity: [Critical/High/Medium/Low/Informational]
Evidence: [REPRODUCTION OR REVIEW]
Required correction: [OUTCOME, NOT PRESCRIPTIVE GUESS]
Assigned agent: [OWNER]
Files/resources: [SCOPE]
Retest: [EXACT CHECKS]
Loop count: [CURRENT / MAX]
~~~

## Loop Controls

- Simple: 2; medium: 4; complex: 6.
- Do not repeat an approach without new evidence.
- Do not reopen approved scope for optional improvements.
- Stop at the maximum and report the blocker and options.
- Critical work or unresolved unclear positioning requires human review.