plan-verify

Verify implementation plan claims against the current codebase.

2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/jscott3201/ai-agent-skills --skill plan-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-verify
Source: https://github.com/jscott3201/ai-agent-skills/tree/main/skills/plan-verify
Command: npx skills add https://github.com/jscott3201/ai-agent-skills --skill plan-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies and reconciles claims in an implementation plan against the current codebase to prevent drift before work begins.

Core Features & Use Cases

  • Compare plan claims (APIs, file paths, and data flows) with actual code to surface inconsistencies early.
  • Check plan staleness by comparing plan dates with recent code changes and repository state.
  • Provide a structured verification workflow with symbol checks, dependency integrity, and an auditable report.

Quick Start

Provide the plan document and the current codebase to initiate an automated verification pass.

Frequently Asked Questions about plan-verify

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

FAQPage Schema
How do I verify an implementation plan against a codebase for API and file path discrepancies?

Plan staleness occurs when implementation plans fall behind recent code changes. Detect staleness by comparing the plan date with repository state and recent commits, ensuring the plan reflects the current evolving codebase before you code.

How do I check if an implementation plan is stale compared to recent repository changes?

Plan staleness occurs when implementation plans fall behind recent code changes. Detect staleness by comparing the plan date with repository state and recent commits, ensuring the plan reflects the current evolving codebase before you code.

Can I automatically audit dependency integrity and API signatures before coding?

Data flow verification tracks how data moves across modules to ensure plan assertions match actual code. Use grep and strict checks to validate data flows and dependency integrity, producing an auditable report for plan accuracy.

What is the best way to validate data flow assertions across evolving repository modules?

Data flow verification tracks how data moves across modules to ensure plan assertions match actual code. Use grep and strict checks to validate data flows and dependency integrity, producing an auditable report for plan accuracy.

When should I not use automated plan-verification for my codebase?

Begin plan-verification by providing the plan document and the current codebase. This initiates an automated verification pass that checks API signatures, file locations, and dependency integrity to surface inconsistencies early.