verification-debt-audit

Audit verification debt across TODO evidence, waivers, and code hygiene.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/belluga/delphi-ai --skill verification-debt-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-debt-audit
Source: https://github.com/belluga/delphi-ai/tree/main/.cline/skills/verification-debt-audit
Command: npx skills add https://github.com/belluga/delphi-ai --skill verification-debt-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit verification debt across TODO evidence, tactical-note drift, waivers, and inline code TODO hygiene before closure.

Core Features & Use Cases

  • Structured audit workflow: frames active TODOs, checks evidence completeness, waivers, promotion discipline, and code TODO hygiene.
  • Promotes durable knowledge: surfaces promotion of decisions into module docs and eliminates knowledge buried in tactical notes.
  • Actionable outcomes: produces an audit outcome with severity, evidence path, and fix options for material debt, plus artifact references.
  • Use Case: When preparing a release that touches shared contracts or cross-module changes, run this audit to surface and resolve verification debt before closure.

Quick Start

Start the verification debt audit by running the guided workflow against the current branch to surface TODO evidence and generate remediation recommendations.

Frequently Asked Questions about verification-debt-audit

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

FAQPage Schema
What is verification debt and how does an audit check for TODO evidence?

Verification debt is unresolved TODO evidence, tactical-note drift, and waiver accumulation. An audit checks for it by framing active TODOs, verifying evidence completeness, and reviewing code TODO hygiene before closure.

How do I audit code TODO hygiene and tactical-note drift before a release?

Run a guided audit workflow against your current branch to frame active TODOs, check evidence completeness, detect tactical-note drift, and promote durable knowledge into canonical module docs to ensure closure.

When should I run a verification debt audit for cross-module changes?

Run a verification debt audit when preparing a release that touches shared contracts or cross-module changes. It surfaces and resolves debt signals to ensure clean closure and proper governance.

What does a verification debt audit output for unresolved TODO governance issues?

The audit outputs an actionable outcome with severity classification, evidence path, and fix options for material debt. It also provides artifact references and guides escalation for unresolved debt signals.

Can I use this audit to promote decisions from tactical notes into canonical docs?

Yes, the audit explicitly promotes durable knowledge by surfacing decisions buried in tactical notes and ensuring they are promoted into canonical module docs to eliminate knowledge drift.