audit

Run a single-document audit on the specification file. The audit checks atomicity, testability, requirement prefixes, NFR measurability, and traceability, then presents each finding with a recommended fix for you to approve, modify, defer, or dismiss.

Use the reconciliation audit mode, which checks the ticket or plan against ground truth: schema and migrations, scripts and commands, and referenced documents. It returns a Go verdict when assumptions hold or Blocked with the named false assumptions.

An audit reviews pipeline documents and plans, not delivered code. It checks artifacts like PRDs, specifications, and tickets for quality and cross-stage consistency. For delivered code, use code-review, quality-review, or security-review instead.

Yes, the skill adapts to whatever artifacts exist in .gener8v/. With only a PRD it produces limited findings, mostly missing-specification gaps, which is still useful for planning next steps. It never generates the missing artifacts itself.

The audit report is written before the first finding is discussed, so nothing is lost. Findings still marked Open are the ones remaining, and the Resolution Log records every decision already made, letting you resume from the dated report file.

The fix likely went to a legacy per-area ticket file that the state script ignores once a ticket directory exists. Apply the fix to the individual TICKET-NNN.md file inside the directory, then re-run lint to confirm it clears.