plan-audit

Audit vd:plan outputs against the codebase and stated goals.

5|Updated May 2, 2026
One-click install
npx skills add https://github.com/vanducng/skills --skill plan-audit-vanducng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-audit
Source: https://github.com/vanducng/skills/tree/main/skills/plan-audit
Command: npx skills add https://github.com/vanducng/skills --skill plan-audit-vanducng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Independent plan auditing verifies that a vd:plan output remains aligned with the real codebase and stated goals, catching gaps that a single planning pass may miss.

Core Features & Use Cases

  • Spawns a clean-context subagent to audit plan files in isolation, without leaking prior conversations.
  • Checks cross-phase consistency, codebase drift, and realism of success criteria against the repository.
  • Produces a structured findings report and an audit artifact stored under the plan's reports/ directory for traceability.
  • Respects decisions.md by excluding non-goals from findings when present.

Quick Start

Run vd:plan-audit on a plan directory after planning to generate an independent audit report.

Frequently Asked Questions about plan-audit

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

FAQPage Schema
How do I verify project plan readiness against the real codebase?▼

Plan auditing verifies project plan readiness by spawning a clean-context subagent to check cross-phase consistency and validate success criteria against the actual codebase. It detects codebase drift and outputs a structured report with severity and actionable fixes.

What is an independent plan audit and how does it work?▼

An independent plan audit evaluates a plan output in isolation using a clean-context subagent. This mechanism prevents leaking prior conversations, ensuring the audit checks cross-phase consistency, codebase drift, and success criteria realism objectively.

How do I audit a plan directory step by step?▼

To audit a plan directory, run the audit command on the plan files after planning. It spawns an isolated subagent to analyze the directory, respects decisions.md by excluding non-goals, and generates a structured audit artifact stored under the plan's reports directory.

Why does my project plan have codebase drift and cross-phase inconsistencies?▼

Codebase drift and cross-phase inconsistencies occur when a single planning pass misses gaps between the real codebase and stated goals. Independent plan auditing catches these gaps by verifying the plan against the repository in an isolated context.

Can I exclude non-goals from the plan audit findings?▼

Yes, the audit respects decisions.md by excluding non-goals from findings when present. This ensures the structured findings report focuses only on actual codebase drift and cross-phase consistency issues relevant to stated goals.

What is the best way to trace plan audit findings over time?▼

The best way to trace plan audit findings is using the audit artifact stored under the plan's reports directory. This structured report provides traceability for codebase drift checks and cross-phase consistency validations over multiple audit runs.