log-decisionlisted

# Log Decision Help the user capture a Decision Record for a significant, costly-to-change decision. If invoked via `/log-decision`, use `$ARGUMENTS` as the title if provided; otherwise ask for one. If triggered by a conversation, say something like: _"This looks like a significant decision — would you like me to draft a Decision Record (DR)?"_ Wait for confirmation before proceeding. > **Not sure yet?** If the user is still exploring options or hasn't settled on a direction, suggest `/decide` instead — it's a thinking-partner skill for working through the problem before documenting it. ## Execution Steps ### 1. Gather Information Use `AskUserQuestion` for each question — ask one topic area at a time. Do not present all fields at once. Start with the essentials; ask about optional fields only if the user is engaged in the detail. **If the user has just come from a `/decide` session**, the Context and Problem Statement, Forces and Constraints, and Considered Options will already be established in the conversation. Confirm the key points rather than re-asking them, and move straight to the Decision field and any gaps. **Essentials** (always required): | Field | Guidance | |---|---| | **Title** | Short phrase representing the problem and solution, e.g., "Use PostgreSQL as primary datastore" | | **Context and Problem Statement** | What situation led to this decision? What problem are you solving? If there are relevant code locations, issues, or tickets that provide conte