delivery-readiness-auditlisted

# Delivery Readiness Audit ## Purpose / When to Activate 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: - **AC internal consistency** — catches missing columns, undeclared endpoints, broken cross-references within a story - **Pending revisions** — catches deferred work flagged in backlog notes but not yet captured as stories --- ## Process ### 1. AC internal consistency — spot-check READY stories For each story identified as "ready to deliver" by Section 1: 1. Open the story artefact file 2. Build an inventory of all resources **declared** by schema/setup ACs: columns, tables, endpoints, queues, secrets, cron triggers 3. Scan all other ACs for resources **referenced** but not in the inventory 4. Flag any reference to a column, endpoint, queue, table, or resource that is not declared elsewhere in the same story **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 revis