AI Feature Launch Check

Iron Law: Do not output GO if any checklist item is ❌. A written exception in the Decision Record with an owner and deadline is required for every ⚠️ item. Verbal assertions do not count as evidence for any item.

Run the unified pre-production launch checklist from the AI Playbook (Layer 4 §4.1). This consolidates the pre-flight questions, pre-production gate, kill-switch tests, and adversarial test catalog into one launch review.

Procedure

1. Ask the user for the feature slug. Look for the Decision Record at docs/ai-decisions/<feature-slug>.md.
   • If it does not exist: stop. Tell the user to run /ai-decision-record first. Do not proceed without one.
2. Read the Decision Record. Cross-check every item below against what the record says.
3. For each checklist item below, ask the user to show evidence, not assert compliance. Examples of evidence:
   • "Output Contract implemented" → point to the validation code; read it.
   • "Eval set" → point to the file; show the size and a sample.
   • "Kill switch tested" → show the test run log.
4. Mark each item: ✅ verified / ⚠️ partial / ❌ missing.
5. Do not pass the launch check if any item is ❌. Partial is allowed only when the user provides a written exception in the Decision Record with an owner and a deadline.
6. Produce a launch decision: GO / NO-GO / GO-WITH-EXCEPTIONS with a written rationale.