What problem does it solve? After implementing a UI feature, it is hard to know whether the code actually does what was requested, whether edge cases like loading and error states are covered, and whether unrelated changes crept into the branch. This Skill performs a behavioral comparison of the implementation against the original spec and produces a structured verdict. ## Core Features & Use Cases - Requirements Verification: Parses the original ticket, task description, or plan output and checks each stated and implicit requirement (loading, error, empty states, accessibility) against the branch diff. - Scope Creep Detection: Flags unrequested changes such as modified shared helpers, new dependencies, or unasked-for refactors, and raises decision memos for human judgment. - Structured Verdict Report: Emits a machine-consumable validation report with PASS, FAIL, or BLOCKED verdicts, routing human-only gaps (manual visual checks) to BLOCKED instead of wasting remediation cycles. - Use Case: Before opening a PR for a new settings page, run the skill against the original Linear ticket to confirm every acceptance criterion is implemented, no unrelated files changed, and required tests exist. ## Quick Start Ask the AI to validate this feature against the original ticket or task description and report any gaps or unrequested changes.
