decision-loglisted

# Decision log Decisions made in chat are forgotten by next week. This skill writes them down **before** the work starts. ## When to use - A plan is approved, or an option is chosen over another. - Something changes: price, scope, tool, supplier, process or policy. - Before any action that is hard to undo: publishing, sending, deleting, paying. ## Steps 1. **Open or create `DECISIONS.md`** at the project root. 2. **Assign the next ID** (`D-001`, `D-002`, …). Never reuse or renumber IDs. 3. **Write the entry** with the template below. Keep it short, but include rejected options: they are what future readers need most. 4. **Set the status:** - `PROPOSED`: waiting for approval - `CONFIRMED`: approved, by whom - `CHANGED`: replaced by a later decision; link it - `DISCARDED`: rejected, with the reason 5. **If the decision replaces an earlier one,** update the earlier entry's status to `CHANGED → D-0XX`. Do not delete it. 6. **Only then** continue with the work. If the status is `PROPOSED`, ask for approval first. ## Template ```markdown ## D-0XX · [Short title] — [STATUS] ([date]) **Context:** [what situation forced a decision] **Decision:** [what was decided, in one or two sentences] **Why:** [the reasons, with data if available] **Rejected options:** [option — reason] **Risks:** [what could go wrong and the cost] **Owner:** [person] · **Review on:** [date or trigger] ``` ## Quality checks - The entry makes sense to someone who was not in the conversati