GovZero Plan Audit

Compare three claims before code is written:

declared intent <-> scoped requirements <-> execution plan

The repository decides whether those artifacts are ADRs, issues, briefs, specs,
or plan files. The audit diagnoses alignment; it does not silently rewrite any
of them.

Discovery and fallback

Prefer, in order:

1. The project's own plan-audit command and its receipt, when one exists.
2. Repository tooling that resolves the intent, the scoped work item, and the
   plan as linked artifacts.
3. The three documents read directly, compared against the current tree.

The third rung is the floor and needs only a file reader. Missing or ambiguous
authority is recorded as a finding at every rung; it is never resolved by
substituting a more convenient document.

Workflow

1. Locate the authoritative intent, the scoped work item, and the plan. Record
   missing or ambiguous authority as an audit finding rather than choosing a
   convenient substitute.
2. Read intent first. Extract the problem, promised capabilities, constraints,
   rejected outcomes, integration points, and acceptance conditions without
   reading the proposed implementation.
3. Read the scoped requirements. Check objective match, complete intent
   coverage, explicit exclusions, path or component boundaries, acceptance
   criteria, and verification requirements.
4. Read the plan. Check that every scoped requirement has an executable step,
   every planned edit is allowed, denied surfaces remain untouched, dependencies
   and ordering are feasible in the current tree, and final verification proves
   the acceptance criteria.
5. Record each comparison as Aligned, Drifted, Missing, or Not Applicable with
   file-and-line citations. Separate scope gaps from scope creep.
6. Present a PASS only when no Drifted or Missing item remains. Otherwise return
   FAIL with a specific recommendation to correct the intent, scope, or plan.

Output

Produce separate intent-to-scope and scope-to-plan tables, a cited gap list,
actionable corrections, and a PASS/FAIL verdict. If the repository defines an
audit receipt format, write it only after the semantic report is complete and
include the audited artifact identities or hashes.