What problem does it solve? After implementing a plan, code often drifts from the original design, introduces security or reliability risks, or breaks existing conventions. This Skill systematically compares actual implementation work against the plan to catch drift, dangerous decisions, architecture violations, and pattern misuse before they compound. ## Core Features & Use Cases - Plan Drift Detection: Uses parallel sub-agents to verify each planned change matches the actual code, flagging missing implementations, intent mismatches, and unplanned scope creep. - Safety & Quality Scanning: Checks changed files for security risks (injection, hardcoded secrets), performance issues (N+1 queries, missing pagination), reliability gaps, and data safety hazards. - Structured Findings & Interactive Triage: Produces a severity-ranked report (CRITICAL/WARNING/OBSERVATION) with impact ratings and fix options, then walks through each finding interactively to apply fixes, record lessons, or skip. - Use Case: After finishing phase 3 of a feature plan, run the review to confirm the new auth handler uses parameterized queries as planned, catch an unplanned API endpoint, and triage each finding with concrete fix options. ## Quick Start Ask the assistant to review the implementation of the current change plan against what was actually built, for example by saying: review the implementation for the current change and triage any findings.
