Spot-check AC internal consistency and scan for pending revisions on delivery-ready stories. Activated by `/gaai-status --audit` as Section 5. Complements the standard status checks with depth checks that standard status skips for speed.
Activate via /gaai-status --audit. This skill runs after the standard status sections (1–4) have already identified delivery-ready stories, memory staleness, and framework health.
This skill adds two depth checks that standard status skips for speed:
For each story identified as "ready to deliver" by Section 1:
Example of what this catches:
orders.cancelled_at for filtering, but AC4 (schema migration) doesn't list that columnusers.api_token but it's missing from the migrationSeverity: CRITICAL if it would cause the Delivery Agent to produce incomplete code.
Scan all backlog item notes fields for patterns indicating unresolved work:
Patterns to match:
DEC- references followed by a pending action descriptionFor each match:
Produce a summary:
For issues safe to correct (missing AC metadata, column alignment), list them as "auto-fixable" in the report. Discovery or the human decides whether to apply fixes — this skill reports only.
### Section 5 — Delivery Readiness
**5a. AC Consistency (READY stories)**
| Story | Issue | Severity |
|---|---|---|
| E01S03 | AC5 uses `orders.cancelled_at` — missing from AC4 migration | CRITICAL |
Verdict: PASS | N issues found
**5b. Pending Revisions**
| Backlog Item | DEC | Pending Action | Story Exists? |
|---|---|---|---|
| E02S04 | DEC-{N} | auth middleware refactor to support RBAC | No |
**5c. Delivery Verdict**
N stories ready. M critical, K important issues.
READY FOR DELIVERY | ISSUES TO RESOLVE FIRST
This skill must NOT:
/gaai-status Sections 1–4 (staleness, dependency graph, backlog counts)If an AC can't survive a cross-reference check, Delivery will produce broken code. Catch it here.