qa-plan

The audit applies a 12-point adversarial review to a TDD plan document or GitHub issue body, checking diagnosability and artifact backing, then emits a PASS or HOLD verdict with detailed per-check findings.

Adversarial gatekeeping for TDD plans is a strict review process that prevents plan review bias by enforcing objective criteria and artifact requirements, ensuring plans are diagnosable and reviewable before implementation begins.

You enforce artifact requirements in a TDD plan review by applying an adversarial audit that checks strict provenance and artifact backing, producing deterministic PASS or HOLD verdicts with no partial credit.

Yes, you can use a GitHub issue body as input for a TDD plan audit, as the review process reads plan documents or GitHub issue bodies and applies its 12-point audit to emit a verdict.

Your TDD plan audit returns a HOLD verdict because the review process is HOLD-default, meaning any failure across the 12-point adversarial checks will prevent a PASS until all findings are resolved.

No, the TDD plan audit does not give partial credit; it produces deterministic PASS or HOLD verdicts based on strict objective criteria across all 12 adversarial checks.