What problem does it solve? After implementation, delivered code often diverges from the approved specification, architecture decisions, or plan without anyone noticing. This Skill systematically compares normative intent against delivered artifacts so mismatches are caught and classified before successful closeout. ## Core Features & Use Cases - Requirement-to-Evidence Mapping: Maps each approved requirement to implementation evidence, verification evidence, and documentation, classifying every mismatch (missing implementation, unspecified behavior, stale plan, stale tests, stale docs). - Structured Drift Verdicts: Produces a drift report with a clear verdict (ALIGNED, ALIGNMENT_REQUIRED, BLOCKED, UNVERIFIED) that gates successful closeout. - Read-Only Audit Authority: Operates with read-only access to source, runtime, and data, writing only the approved drift report path. - Use Case: After a feature changes API contracts and authentication flows across five files, run this audit before closeout to confirm the implementation, tests, and docs still match the approved spec and to surface any unapproved behavior. ## Quick Start Audit the current Work Block's implementation against its approved specification and produce a drift report with a verdict before closeout.
