What problem does it solve? Specs drift away from actual code after implementation, leaving teams without traceability between requirements and behavior. This Skill audits a LiveSpec feature by comparing spec.md requirements (FR/AC) against @spec anchors in code, validating tree structure, spec quality gates, visual baselines, and Penflow contracts, then produces a dated gap report. ## Core Features & Use Cases - Spec vs Code Verification: Maps every FR/AC to @spec anchors and test files, classifying each as Verified, Partial, Missing, or Drifted. - Tree & Quality Gates: Validates .specs/ system files, feature naming, completeness, Gherkin/Mermaid quality gates, and README sync. - Visual Governance: Detects pixel drift against Playwright baselines, classifies baseline staleness (mockup hash, browser version), checks design fidelity and theme token compliance, and enforces Penflow contract certification. - Use Case: After implementing a notifications feature, run the check to confirm all six FRs have code evidence, catch a diverged dashboard baseline, and write .specs/features/004-notifications/checks/<date>-check.md. ## Quick Start Ask the AI to run /spec-check on your feature, for example: verify the 004-notifications feature against its spec and show me the gap report.