plan-auditor

To validate code against a plan, you perform an evidence-based code audit by searching the repository for implementation artifacts and comparing them against the plan's requirements. This static analysis produces a structured Plan Validation Report detailing coverage, gaps, and pass/fail status per requirement.

Evidence-based code auditing is a static analysis process that searches your repository for artifacts corresponding to plan steps. It anchors the audit scope using frontmatter-defined plan metadata, comparing actual code against expected steps to produce a structured validation report with explicit evidence.

To check plan alignment during a codebase refactor, you validate the updated code against your defined plan by loading the plan file, parsing its requirements, and auditing the repository for matching implementation artifacts. This generates a Plan Validation Report detailing coverage gaps and recommendations.

Static code validation requires no external dependencies to parse plan metadata. The skill directly enforces frontmatter-defined plan metadata to anchor the audit scope, loads the plan file, and searches the repository for implementation artifacts without needing additional setup.

You can use code auditing for compliance checks by applying static analysis to verify that repository artifacts correctly implement a defined plan. The audit loop searches for implementation evidence, marks requirements as Pass, Fail, or Partial, and outputs a structured report detailing coverage gaps.

The best way to report coverage gaps after a code audit is to generate a structured Plan Validation Report. By comparing implementation artifacts against plan requirements during static analysis, the report explicitly details pass, fail, or partial status per requirement alongside actionable recommendations.