Phase 5 - Closure

Closure turns raw test results into a structured verdict and a stakeholder-ready summary. If there are failures, /qa-triage classifies them by severity and issues a ship/no-ship decision before the summary is written.

---

Skills in this phase

Skill	When to run	Purpose
/qa-triage	Only if failures exist	Classify failures by severity, issue ship/no-ship verdict
/qa-coverage	Release readiness gate	Confirm all requirements were tested
/qa-report	Final step, every cycle	Aggregate all results into qa-summary.md

---

Step 1 - Triage failures (/qa-triage)

If any domain produced failures, run /qa-triage before writing the summary. It reads all execution reports, cross-references failures against your schema and requirements, and categorises each one.

Severity model:

Priority	Criteria	Verdict
P0 - Critical	Data loss, security vulnerability, complete feature broken, WCAG critical	No-ship
P1 - High	Core user journey impaired, major perf threshold breached, WCAG serious	No-ship (unless explicitly accepted)
P2 - Medium	Significant issue with a workaround, moderate a11y violation	Ship with ticket
P3 - Low	Minor visual issue, cosmetic a11y violation	Ship with ticket

Output - qa-triage.md:

## 2026-05-26
### Executive summary
Failures: 3  |  P0: 0  |  P1: 1  |  P2: 1  |  P3: 1
Verdict: NO-SHIP - one P1 must be resolved before release.

---

Step 2 - Release readiness check (/qa-coverage)

In Closure mode, /qa-coverage cross-references the executed tests against qa-plan.md to confirm every planned requirement was actually tested. This is the formal release readiness gate.

Output: Updated qa-coverage.md with a release readiness verdict

---

Step 3 - Generate the summary (/qa-report)

Run /qa-report as the final step of every cycle. It aggregates results from all domains and the triage report into a single qa-summary.md dashboard.

Inputs consumed:

File	Source
qa-plan.md	Cycle scope and objectives
qa-reports/api/api-report.json	API test results
qa-reports/ui/ui-report.html	UI test results
qa-reports/a11y/a11y-report.json	Accessibility violations
qa-reports/perf/perf-report.json	Performance metrics
qa-triage.md	Failure categorisation and verdict
qa-coverage.md	Release readiness gate result

Output - qa-summary.md:

## 2026-05-26 - QA Summary
Project: my-app  |  Cycle: Sprint 12
Domains tested: API, Accessibility
Overall verdict: SHIP

API:           47 tests passed, 0 failed
Accessibility: 3 pages audited, 0 violations

This file is safe to share with product managers, release managers, and stakeholders.

---

Cycle complete - what's next?

Scenario	Next action
All passed, shipping	Archive qa-summary.md and close the cycle
Failures fixed, re-testing needed	Re-run only the failed domains via /qa-exec, then repeat Closure
New cycle starting	Run /qa-impact in Phase 2 to track what changed

---

Phase gate

Phase 5 is complete when:

• [x] /qa-triage has been run (if there were failures) and verdict is recorded
• [x] /qa-coverage confirms release readiness
• [x] qa-summary.md exists with the current cycle's results
• [x] Stakeholders have been notified of the verdict