plan-validating

Validates that implementation plans were correctly executed against git history and automated checks.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/dsonyy/dotfiles --skill plan-validating-dsonyy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-validating
Source: https://github.com/dsonyy/dotfiles/tree/main/skills/plan-validating
Command: npx skills add https://github.com/dsonyy/dotfiles --skill plan-validating-dsonyy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After implementing a plan, it is hard to know whether every phase was actually completed, whether automated checks pass, and whether the code deviates from what was specified. This Skill systematically verifies implementation work against the original plan before it ships. ## Core Features & Use Cases - Context Discovery: Locates the implementation plan and gathers evidence from recent git commits and diffs to understand what was changed. - Systematic Validation: Checks each plan phase for completion, runs automated verification commands like build, test, and precommit, and assesses manual testing criteria. - Validation Report Generation: Produces a structured report covering implementation status, verification results, deviations from the plan, potential issues, and manual testing steps. - Use Case: After finishing a multi-phase feature implementation and committing the changes, run this Skill to confirm all success criteria pass, catch missing test coverage, and document deviations before creating a pull request. ## Quick Start Ask the AI to validate that the implementation plan was correctly executed by checking recent commits and running the automated verification commands.

Frequently Asked Questions about plan-validating

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify an implementation plan was completed correctly?▼

Review recent git commits and diffs to see what changed, then run the plan's automated verification commands such as build and test. Compare each plan phase against the actual code and document any deviations or missing items in a validation report.

How to validate code changes against a plan using git?▼

Use git log to list recent commits and git diff across the implementation range to inspect actual changes. Match modified files against the plan's expected file list and confirm success criteria are met before merging.

When should I run plan validation in my workflow?▼

Run validation after implementing the plan and committing changes, but before creating a pull request. Git history gives the validator concrete evidence of what was implemented, making the review more accurate.

What happens if automated verification fails during validation?▼

The failure is documented with its pass/fail status and the root cause is investigated. The validation report lists the issue along with recommendations, such as fixing linting warnings or adding missing test coverage, before merge.

Can plan validation replace manual testing?▼

No. Automated checks confirm builds and tests pass, but manual criteria like UI behavior and integration with existing components still require human verification. The validation report provides clear manual testing steps for the user.