source-command-ff-validate-plan

Validates implementation against plan success criteria and generates a structured validation report.

1|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/redblacktree/fastflow --skill source-command-ff-validate-plan-redblacktree
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-command-ff-validate-plan
Source: https://github.com/redblacktree/fastflow/tree/main/.agents/skills/source-command-ff-validate-plan
Command: npx skills add https://github.com/redblacktree/fastflow --skill source-command-ff-validate-plan-redblacktree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After implementing a plan, it is hard to confirm that every phase was actually completed, that automated checks pass, and that no deviations or regressions were introduced. This Skill systematically compares the executed implementation against the original plan and produces a clear validation report. ## Core Features & Use Cases - Context Discovery: Locates the implementation plan, reviews recent git commits and diffs, and gathers evidence of what was actually changed. - Systematic Verification: Runs automated checks (build, test, lint), verifies each plan phase's completion status, and assesses manual testing criteria. - Validation Report: Generates a structured markdown report covering implementation status, automated verification results, deviations from the plan, potential issues, and manual testing steps. - Use Case: After running an implementation workflow and committing changes, invoke this Skill to confirm the database migration, API endpoints, and tests all match the plan before opening a pull request. ## Quick Start Ask the agent to validate the recent implementation against the plan file and report any deviations or failing checks.

Frequently Asked Questions about source-command-ff-validate-plan

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

FAQPage Schema
How do I validate an implementation against a plan?▼

Provide the plan file path or let the Skill locate it from recent commits. It reviews git history, runs automated checks like build and test commands, and compares actual code changes against each planned phase to produce a validation report.

What does the validation report include?▼

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, and a checklist of manual testing steps.

When should I run plan validation in the workflow?▼

Run it after implementation and commits are complete, since it analyzes git history to understand what changed. The recommended sequence is implement, commit, validate, then generate the PR description.

Can validation work without the original plan file?▼

Yes, if no plan path is provided it searches recent commits for plan references or asks the user. However, validation is most thorough when the full plan with success criteria is available for comparison.

What happens when automated checks fail during validation?▼

Failures are documented in the report with pass/fail status for each command, and the Skill investigates the root cause. It also flags potential issues such as missing indexes or absent rollback handling as recommendations.