plan-validator

Validate a codebase against a plan using static analysis.

39|6|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/ddobrin/gemini-plan-commands --skill plan-validator-ddobrin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-validator
Source: https://github.com/ddobrin/gemini-plan-commands/tree/main/skills/plan-validator
Command: npx skills add https://github.com/ddobrin/gemini-plan-commands --skill plan-validator-ddobrin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill acts as a Quality Assurance Engineer and Code Auditor to verify that a codebase implements a given plan via static analysis, providing evidence-based findings and gap analysis.

Core Features & Use Cases

  • Static plan-based code verification
  • Evidence-based reporting with detailed traces
  • Gap analysis and remediation recommendations

Quick Start

Run the plan-validator skill to audit the current codebase against a selected plan and generate a structured QA report.

Frequently Asked Questions about plan-validator

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

FAQPage Schema
How do I validate that my codebase matches a project plan?

Static plan-based code verification uses static analysis to extract requirements from a plan and search the codebase for matching artifacts. It reports Pass, Fail, or Partial with precise evidence traces for gap analysis.

What is evidence-based code auditing for feature implementations?

Evidence-based code auditing is a QA process that extracts plan requirements and searches the codebase for corresponding artifacts. It provides structured reporting with detailed traces, gap analysis, and remediation recommendations.

Can I use static analysis to verify a refactoring against a plan?

Yes, static analysis can verify refactors against a plan. The audit applies to feature implementations and refactors, searching the codebase for required artifacts and reporting detailed evidence traces for verification.

How do I generate a QA report for gap analysis in my codebase?

To generate a QA report for gap analysis, run an audit against a selected plan to compare extracted requirements with codebase artifacts. It outputs structured reporting with Pass, Fail, or Partial statuses and precise evidence.

Does the plan-validator require any dependencies to run a code audit?

No, the plan-validator does not require any dependencies to run a code audit. You can execute the skill directly on your current codebase against a selected plan to generate structured QA findings.

What's the best way to find missing requirements after a feature implementation?

The best way to find missing requirements is to perform a static analysis audit that extracts requirements from the plan and searches for corresponding artifacts. It reports Partial or Fail statuses with precise evidence for gap analysis.