spec-conformance-audit
Installation
SKILL.md
Spec Conformance Audit
Determine whether the implementation matches what was authorized.
Audit only. Do not edit files, apply fixes, commit, publish, or mutate external systems unless the user separately asks for implementation.
Goal
Trace every material requirement and protected constraint to observable implementation evidence, while identifying work that changed behavior beyond the agreed scope.
Establish the Contract
Use the smallest authoritative source set that defines the work:
- the user's latest explicit decisions and corrections
- the named specification, issue, plan, or selected review feedback
- repository instructions and established contracts that the work did not authorize changing
Later explicit decisions override earlier proposals. A suggestion is not a requirement merely because it appears in a plan or prior model response. Current implementation behavior is evidence, not automatically the intended contract.