Delivery Readiness Audit

Example of what this catches:

• AC5 uses orders.cancelled_at for filtering, but AC4 (schema migration) doesn't list that column
• AC7 references users.api_token but it's missing from the migration

Severity: CRITICAL if it would cause the Delivery Agent to produce incomplete code.

2. Pending revisions scan

Scan all backlog item notes fields for patterns indicating unresolved work:

Patterns to match:

• "will be revised", "pending revision", "needs review"
• "story to generate", "story E0xS0x to generate", "to be created"
• "TODO", "to replace", "to migrate", "needs update"
• DEC- references followed by a pending action description

For each match:

• State the backlog item ID, the DEC reference (if any), and the pending action
• Check whether a corresponding story already exists in the backlog
• Flag as IMPORTANT if no story exists yet

3. Delivery verdict

Produce a summary:

• Count of stories truly ready (all deps met + ACs internally consistent)
• Count of issues by severity (CRITICAL / IMPORTANT / MINOR)
• Verdict: READY FOR DELIVERY (0 critical issues) or ISSUES TO RESOLVE FIRST (list critical issues)

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.

Output Format

### 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

Quality Checks

• Every finding references a specific story ID, AC number, and resource name
• No vague findings ("something might be wrong" is invalid)
• Severity is explicit: CRITICAL (blocks Delivery), IMPORTANT (should fix), MINOR (cosmetic)
• No false positives — only flag cross-references that are genuinely missing
• The report is additive to standard status — never repeats Sections 1–4

Non-Goals

This skill must NOT:

• Repeat checks already done by /gaai-status Sections 1–4 (staleness, dependency graph, backlog counts)
• Fix issues (report only — Discovery or human decides)
• Rewrite artefacts or memory
• Make prioritization decisions about delivery order

If an AC can't survive a cross-reference check, Delivery will produce broken code. Catch it here.