log-decision

name	log-decision
description	Log a Decision file with reasoning preserved. Use when the user says "I decided" or "let's go with" and the decision has real reasoning behind it.
trigger_keywords	["decided","decision","going with","let's go with","picked","chose"]

log-decision

The user just made (or is about to make) a Decision worth recording. Help them log it via oc decision new.

Steps

1. Identify the decision in plain language
2. Identify the reason — what made this the right call
3. Identify the options considered (at least 2; the rejected ones matter)
4. Identify any prior Decisions this supersedes (search the canon for related Decisions)
5. Identify the consequences — what this enables or constrains
6. Run: oc decision new --title "<short>" --decision "<one paragraph>" --reason "<why>" --option "<rejected A>" --option "<rejected B>" --consequence "<consequence>" --replaces <prior-id-if-any>

When NOT to invoke this skill

• Trivial choices (which library to import, which keybinding to use). The bar is "future-you in 3 months will ask why" — if the answer is "obvious", don't log it.
• Choices already implicit in code or commits. Git history captures those.
• Tooling picks unless the choice was contested. "I used uv" is not a Decision; "I picked uv over pip after benchmarking" might be.

Output

A Decision file at Decisions/DEC-<date>-<NNN>.md with reasoning, options, replaces edges, consequences. Past-you in 3 months can read it and understand the call.