source-command-validate-plan

Run the validate_plan command after implementation and commits are complete. It reads the plan, inspects recent git commits and diffs, runs automated verification commands, and produces a report comparing planned versus actual changes.

The report covers per-phase implementation status, automated verification results for build, test, and lint commands, code review findings listing matches and deviations from the plan, potential issues, manual testing steps, and recommendations.

Run it after implementing the plan and creating commits, but before generating a PR description. The recommended sequence is implement_plan, commit, validate_plan, then describe_pr, since validation analyzes git history.

Yes. When starting fresh, the skill discovers context by locating the plan from recent commits or user input, then uses git log and diffs plus parallel research tasks to reconstruct what was implemented.

Automated checks cannot verify manual success criteria such as UI behavior or integration with external systems. The report explicitly lists manual testing steps that a human must perform to complete validation.