hex-decidelisted

<!-- # sync-safe --> # /hex-decide — Structure a Decision ## Step 1: Identify the Decision If the user provided a topic, use it. Otherwise ask: "What do you need to decide?" Keep the scope tight. If the topic is broad ("what to do about the project"), ask: "What specific question needs an answer?" ## Step 2: Gather Context Search memory and project files for relevant context: ```bash hex memory search "decision topic keywords" ``` Read any relevant project context files, people profiles, or past decisions. ## Step 3: Build the Decision Document Create a structured decision document with this format: ```markdown # Decision: {topic} **Date:** {today} **Status:** Draft ## Context {Why this decision needs to be made now. 2-3 sentences max.} ## Options | Option | Pros | Cons | Risk | |--------|------|------|------| | A: {name} | {benefits} | {drawbacks} | {what could go wrong} | | B: {name} | {benefits} | {drawbacks} | {what could go wrong} | | C: {name} | {benefits} | {drawbacks} | {what could go wrong} | ## Recommendation {Which option and why. Be direct.} ## What Changes {If we go with the recommendation, what happens next? Who needs to know?} ``` Rules: - Always present 2-3 options. Never just one. - One option can be "do nothing" if that's a valid choice. - Pros and cons must be specific, not generic. "Faster" is bad. "Saves 2 hours per week" is good. - The recommendation must pick a side. No "it depends." ## Step 4: Present and Discuss Show the decision do