decision-loglisted

# Decision Log Preserve the reasoning behind consequential decisions so future humans and agents can understand why a workspace evolved the way it did. Use `DECISIONS.md` as lightweight project memory, not as a changelog or a record of everything that happened. ## Workflow When a decision emerges during work: 1. Wait until a decision has actually been made. Do not log ideas, open questions, or alternatives that are still being explored. 2. Apply the decision gate below. 3. If the decision does not pass the gate, continue the work without mentioning the decision log. 4. If it passes, locate an existing `DECISIONS.md` in the relevant workspace. 5. If no decision log exists, propose creating `DECISIONS.md`. Do not create one proactively before the first qualifying decision. 6. Once a decision log exists, record future qualifying decisions as part of the work without asking for confirmation each time, unless the user has requested otherwise. 7. Put new decisions at the top of the log, immediately below its introductory text. Do not interrupt work merely to search for something worth recording. Decisions should emerge from the work; never manufacture decisions to justify using this skill. ## Decision gate Automatically record a decision only when it passes all of these tests: **Durable** The choice is expected to affect future work, not only the current action. **Material** The choice meaningfully changes, establishes, rejects, or clarifies a direction, assumption, r