gap-audit-then-fix

A codebase gap audit compares your repository artifacts against a formal specification to verify existence and correctness. It categorizes uncovered gaps by severity and generates a durable GAPS.md registry with per-file remediation guidance.

Tracking and fixing codebase gaps is handled by dispatching actionable fixes for P1 and P0 severities in parallel while maintaining a living GAPS.md registry. This registry acts as a checklist-driven audit output with targeted per-file remediation tasks.

A gap audit applies when a formal specification exists but implementation coverage is uncertain. It extracts required artifacts from the specification into an audit checklist, verifies each artifact, and surfaces gaps with assigned severities for targeted fixes.

A gap audit generates a durable GAPS.md registry for ongoing codebase quality tracking. This living registry documents severities, verification passes, and per-file remediation guidance so teams can resolve specification gaps methodically over time.

A spec review classifies codebase gaps by verifying the existence and correctness of each required artifact, then categorizing gaps by severity. It prioritizes P0 and P1 gaps for immediate parallel fixes while logging lower severity issues in the registry.

To start a gap audit session you need a formal specification detailing required artifacts and a codebase to evaluate. The audit extracts the specification requirements into a checklist, verifies implementation coverage, and outputs a GAPS.md registry to begin fixes.