skills.rest
atomicinnovation
atomicinnovationOFFICIAL
Explore all skills by this author →
GitHub

validate-plan

Validate implementation plans against git history and test results.

30|1|Updated Mar 15, 2026
Search Tags:#git#qa#reporting#plan-validation#implementation-verification#automated-tests
One-click install
npx skills add https://github.com/atomicinnovation/accelerator --skill validate-plan-atomicinnovation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validate-plan
Source: https://github.com/atomicinnovation/accelerator/tree/main/skills/planning/validate-plan
Command: npx skills add https://github.com/atomicinnovation/accelerator --skill validate-plan-atomicinnovation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill verifies that an implementation plan was executed as intended by checking success criteria, comparing planned changes to the actual codebase and test results, and surfacing deviations or missing work.

Core Features & Use Cases

  • Plan-to-code validation: Parse a plan file, enumerate expected file and behavioral changes, and compare them against git history and the current repository state.
  • Automated verification: Run project test and check commands, record pass/fail outcomes, and investigate failures against plan specifications.
  • Reporting and persistence: Produce a structured validation report with YAML frontmatter and save it to the configured validations directory for traceability and follow-up.

Quick Start

Run validate-plan against the plan file path to compare the plan to the repository state and generate 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 that a software implementation plan matches the actual code changes?▼

Plan verification compares expected file and behavioral changes from a plan file against git history and the current repository state. It parses the plan, enumerates expected modifications, and identifies deviations or missing work.

Can I automatically run project tests during post-implementation review?▼

Automated verification runs project test and check commands during post-implementation review. It records pass and fail outcomes, then investigates any failures against the original plan specifications to surface deviations.

What is the best way to generate structured validation reports for software development workflows?▼

Structured validation reports are generated with YAML frontmatter and saved to a configured validations directory. This produces traceable documentation comparing planned changes to actual test results for follow-up.

Do I need repository access to validate implementation plans against git history?▼

Repository access is required to validate implementation plans. The process reads plan markdown files, runs project test commands, checks git history, and writes structured validation reports to the configured validations directory.

How does plan-to-code validation handle missing work or unexpected deviations?▼

Plan-to-code validation surfaces deviations and missing work by comparing expected changes from the plan file against the actual codebase and test results. It produces a structured report detailing any discrepancies found.

Related Skills

Explore More Software Engineering Skills→
snake-dev-teamsnake-dev-team

ck:retro

Extract git history and generate sprint retrospective reports in markdown or HTML.

Official
Advanced
ozkanguozkangu

eisenhower-triage

Triage tasks into Eisenhower quadrants with a focus on DO, SCHEDULE, and DELEGATE.

Community
Intermediate
cskirocskiro
7

e2e-testing

Automate Playwright end-to-end test setup, generation, and regression detection.

Community
Advanced
theomonforttheomonfort
3

validate-plan

Validate code changes against plan success criteria and generate a validation report.

Community
Advanced