qa

name	qa
description	Generate a QA checklist from PRD and issues, then guide manual verification with triage routing for findings. Use after code review passes (Phase 7) for final human judgment.

QA Checklist & Manual Verification

Generate a comprehensive QA checklist from the planning artifacts, then guide the human through manual verification. This phase is the final gate before merge.

Process

1. Gather acceptance criteria

Read the planning artifacts to extract testable criteria:

• Read .scratch/prd.md for user stories and implementation decisions
• Read all files in .scratch/issues/ for per-slice acceptance criteria
• Cross-reference with any test files to identify what is already covered by automated tests

2. Generate QA checklist

Build a numbered checklist organized by verification gate:

Functional Correctness

• Does each user story from the PRD work as described?
• Do the happy paths complete successfully?
• Are form submissions, API calls, and state transitions correct?

Edge Cases & Error States

• What happens with empty input, null values, boundary conditions?
• Do error messages appear and are they helpful?
• Does the feature degrade gracefully under unexpected conditions?

Type Safety & Build

• Does pnpm run type-check pass?
• Does pnpm run build succeed?
• Does pnpm run lint pass?

Test Coverage

• Does pnpm run test pass?
• Does pnpm run test:coverage meet the 80% threshold?
• Are there behavioral scenarios not covered by automated tests?

Accessibility (WCAG 2.1 AA)

• Are interactive elements keyboard accessible?
• Do images and icons have meaningful alt text?
• Are color contrast ratios sufficient (4.5:1 normal, 3:1 large)?
• Do form inputs have associated labels?
• Are dynamic content updates announced via aria-live regions?
• Are semantic HTML elements used instead of generic divs/spans?
• Is focus visible and non-trapped in all non-modal contexts?
• Does the axe-core integration test suite pass with zero violations?

3. Present for human walkthrough

Present the checklist to the human. For each item, the human reports:

• Pass — works as expected
• Fail — describe what went wrong

4. Triage findings

When a finding is reported, classify it and route to the correct re-entry point:

Bug / Cosmetic Fix

The implementation has a defect or visual issue.

• Create a new issue in .scratch/issues/
• Re-enter at Phase 6 (TDD Implementation)
• No re-grilling needed

Missing Edge Case / Incomplete Behavior

The feature works for the happy path but misses a scenario.

• Create a new issue in .scratch/issues/
• Re-enter at Phase 5 (Tracer Bullet Slicing) to verify the new issue doesn't conflict with existing slices
• Then proceed to Phase 6

Fundamental Misalignment

The feature works as built, but what was built doesn't match what was needed. The PRD got something wrong.

• Re-enter at Phase 1 (Relentless Grilling) to realign understanding
• Flow through the full pipeline again
• This should be rare if Phase 1 was thorough

5. Approve for merge

When all checklist items pass (or all findings have been triaged and resolved):

• Confirm the feature is ready for merge
• Note any follow-up items that were deferred
• The condensed PRD summary should be included in the PR description