validate-plan

Validate implementation against plan success criteria and generate verification reports.

1|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/dominionism/Noesis --skill validate-plan-dominionism
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validate-plan
Source: https://github.com/dominionism/Noesis/tree/main/assets/skills/validate-plan
Command: npx skills add https://github.com/dominionism/Noesis --skill validate-plan-dominionism

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After executing an implementation 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 compares the plan against the real implementation and produces a structured validation report. ## Core Features & Use Cases - Context Discovery: Locates the plan, reviews recent git commits and diffs, and reads project state and decision files to reconstruct what was implemented. - Systematic Validation: Checks each plan phase for completion, runs automated verification commands like build, test, and lint, and assesses manual testing criteria. - Validation Report Generation: Produces a Markdown report covering implementation status, automated verification results, deviations, potential issues, and manual testing steps. - Use Case: After finishing a multi-phase feature implementation, run this Skill to confirm all success criteria pass, catch missing error handling or regressions, and document remaining manual test steps before opening a pull request. ## Quick Start Ask the agent to validate the implementation of the current plan against its success criteria and produce a validation report.

Frequently Asked Questions about validate-plan

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

FAQPage Schema
How do I verify an implementation matches its plan?▼

Read the plan to list expected file changes and success criteria, then compare against actual git commits and diffs. Run the plan's automated verification commands such as build, test, and lint, and document pass or fail status for each phase.

How to validate code changes after implementing a feature?▼

Check recent commits with git log and git diff to see what changed, run the project's check and test commands, and confirm each plan phase is complete. Then generate a report covering matches, deviations, potential issues, and manual testing steps.

What should a validation report include after implementation?▼

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

Can validation run without the original plan document?▼

Yes, but it is harder. The workflow searches recent commits for plan references or asks the user for the plan path, then reconstructs expected changes from git history and codebase analysis before verifying them.

When should plan validation run in the development workflow?▼

Run validation after implementation and commits are made, since it analyzes git history to understand what changed. It fits between committing changes and generating a pull request description.