AI Feature Decision Record

Iron Law: Do not proceed to implementation without a completed Decision Record written to docs/ai-decisions/<feature-slug>.md. It is a required artifact — not optional documentation.

Walk the user through filling out the Decision Record from the AI Playbook (Layer 3 §3.3). This is a required artifact before building any AI feature.

Procedure

1. Confirm the user is starting a new AI feature, not modifying an existing one. If modifying: load the existing Decision Record and update it; do not start fresh.
2. Ask the questions below one at a time. Do not skip ahead.
3. For each answer, validate it against the playbook's principles. Push back when:
   • The answer suggests AI is being added where deterministic code would work better (cross-check Layer 1 §1.6 Red Flag Matrix).
   • The risk tier proposed is lower than the blast radius justifies (cross-check Layer 2 §2.2 Autonomy Ladder).
   • The pattern (assistant / workflow / agent / autonomous) is more complex than needed (apply Layer 1 §1.4: start one tier below where you think you need to be).
   • No fallback is named.
   • No named human owner.
4. After all questions are answered, write the Decision Record to docs/ai-decisions/<feature-slug>.md in the repo (create the directory if needed).
5. Output a summary of the three biggest risks in the Decision Record and recommend whether to proceed, scope down, or rethink.