Summary
Add an \�udit-test-compliance\ template that audits test code against requirements and validation plan. Answers: do the tests verify what the plan says they should?
Context
PR #35 shipped the \�udit-traceability\ template for cross-document specification drift (D1–D7). The \specification-drift\ taxonomy reserves D11–D13 for test compliance drift types. This is Phase 2 of the specification integrity roadmap.
Scope
New components needed:
- Template: \�udit-test-compliance\ — consumes requirements-document + validation-plan + test code; produces investigation-report
- Protocol: \ est-compliance-audit\ (reasoning) — phased methodology for mapping validation plan test cases to actual test implementations
- Taxonomy extension: Define D11–D13 labels in \specification-drift\ taxonomy (e.g., D11_UNIMPLEMENTED_TEST_CASE, D12_UNTESTED_ACCEPTANCE_CRITERION, D13_ASSERTION_MISMATCH)
Reused components:
- \specification-analyst\ persona
- \investigation-report\ format
- \�nti-hallucination\ + \self-verification\ guardrails
Drift types to define
| Label |
Description |
| D11 |
Test case in validation plan has no corresponding automated test |
| D12 |
Acceptance criterion has no assertion in the test implementation |
| D13 |
Test assertions don't match the expected behavior from the plan |
Acceptance criteria
Summary
Add an \�udit-test-compliance\ template that audits test code against requirements and validation plan. Answers: do the tests verify what the plan says they should?
Context
PR #35 shipped the \�udit-traceability\ template for cross-document specification drift (D1–D7). The \specification-drift\ taxonomy reserves D11–D13 for test compliance drift types. This is Phase 2 of the specification integrity roadmap.
Scope
New components needed:
Reused components:
Drift types to define
Acceptance criteria