audit-impl

To audit code changes against a plan document, compare your feature branch diffs against the originating plan files. This validates implementation coverage, detects scope creep, and generates a GO or NO GO merge verdict with remediation steps.

Checking for scope creep requires comparing completed code diffs against specified plan manifests. This implementation review identifies unexpected changes and missing features, issuing a NO GO verdict with detailed findings if non-compliant changes are detected.

Plan adherence validation works by comparing code diffs against one or more specified plan files. It validates coverage and correctness, ensuring the implementation accurately reflects the original requirements before issuing a merge approval.

Yes, you can verify implementation correctness against multiple plan files. The audit process compares code changes across all specified manifests to ensure complete scope validation and detect any missing requirements or unexpected modifications.

A NO GO verdict during an implementation review means merge approval is denied because remediation is required. It indicates the code changes do not adhere to the plan document, accompanied by detailed findings and steps to fix non-compliant changes.

You need to run a code audit against feature requirements after a developer finishes implementing a feature but before merging. It acts as a final gatekeeper to ensure the code accurately reflects the original plan and prevents missed requirements.