| model | opus |
| name | requirements-audit |
| description | Audit a PR, ticket, spec, or local change against stated requirements and acceptance criteria. |
Requirements Audit
Trace requirements to implementation and tests. Focus on missing, partial, excessive, or contradictory behavior.
Load Rules
Read ~/.claude/rules/question-policy.md, ~/.claude/rules/review-finding-format.md, and ~/.claude/rules/pr-mode-readonly.md when applicable. Use ~/.agents/rules/ under Codex. For full audit procedure, read references/protocol-index.md.
Flow
- Identify source of requirements: Linear, PR body, spec, plan, or user-provided text.
- Build an acceptance-criteria checklist.
- Read relevant implementation, tests, and diffs.
- Classify each criterion as Covered, Partial, Missing, Excess, or Unclear.
- Verify tests would catch important regressions.
- Run adversarial challenge for non-obvious findings.
Output
Findings first, with requirement reference, implementation evidence, test evidence, severity, and concrete fix.