What problem does it solve? During or after implementation, teams lose track of whether the actual code matches the approved plan. This Skill performs a read-only reconciliation between an approved plan, its tasks, and the current repository state, so drift, missing work, and unplanned changes are surfaced with evidence instead of guesswork. ## Core Features & Use Cases - Task-to-evidence tracing: Maps every plan task to concrete evidence in code, tests, configuration, or documentation, classified as complete, partial, missing, stale, blocked, or unplanned. - Drift and gap detection: Identifies stale tasks, unplanned changes, missing validation, and test-first violations without editing plans or source code. - Structured convergence report: Produces a Markdown report with an evidence table, validation status, unplanned changes, and required approvals. - Use Case: After a sprint of implementation, ask the assistant to check the approved plan against the current diff and receive a per-task convergence verdict with cited file and line evidence. ## Quick Start Ask the assistant to compare the approved plan at docs/plans/checkout-redesign.md with the current repository state and report which tasks are complete, partial, or missing.
