What problem does it solve? After implementing a plan, teams often commit code without confirming it actually matches the plan's success criteria, leading to regressions and incomplete features slipping into the codebase. This Skill acts as a quality gate that systematically verifies implementation correctness before any commit. ## Core Features & Use Cases - Plan-to-Code Comparison: Reads the implementation plan, identifies expected file changes and success criteria, then compares actual git diffs against the specification phase by phase. - Automated Verification Execution: Runs the test, build, and lint commands defined in the plan's Automated Verification section and documents pass/fail results. - Structured Validation Report: Produces a markdown report covering implementation status, deviations, potential issues, manual testing steps, and recommendations, then updates the work-item tracker state. - Use Case: After running /implement-plan on a feature branch, invoke /validate-plan to catch a missing database index and failing lint checks before creating commits, keeping git history clean. ## Quick Start Ask the agent to validate the current uncommitted implementation against the plan file at flow/plans/my-feature.md using /validate-plan.
