Quality checks

Managers and engineers verify assigned work against the approved feature card and prototype. Read applicable security rules and accessibility checks.

Before testing

Record the task, revision or preview version, environment and required checks. Use synthetic data. A manager without local code repos can test an approved preview; checks requiring local code or automation must be assigned explicitly.

Evidence

For each check record steps, expected result, observed result, pass/fail/untested and a screenshot when useful. Include device/browser for UI issues. Never include tokens, private contacts or customer data in screenshots.

Automated checks and human manual checks are separate. After automated checks, say "It's testing time" and provide the human's exact next steps. Do not continue to another task silently or mark unperformed checks as passing.

Handoff

• List passed checks and remaining failures or uncertainties.
• Return failures within scope to the task owner.
• Report new bugs or improvements for founder triage and assignment.
• Technical review, founder acceptance and release verification are distinct.
• Retest fixes against the new revision before closing the finding.

See the team workflow for assignment and closure rules.