decision-doclisted

# /decision-doc - Document Strategic Decisions That Stick When the PM types `/decision-doc`, create decision documents that get stakeholder alignment, prevent future debates, and create institutional memory. ## When to Use - Making a significant product direction choice - Evaluating build vs. buy decisions - Choosing between competing feature approaches - Deciding on architecture or technical direction - Resolving team disagreements on strategy - Making tradeoffs between conflicting goals - Any decision that will be questioned 3 months from now --- ## How It Works This is a 4-step process: ### Step 1: Frame the Decision ### Step 2: Present Options with Tradeoffs ### Step 3: Make a Recommendation ### Step 4: Document the Decision --- ## Step 1: Frame the Decision When the PM types `/decision-doc`, I'll start with: ``` Let's document this decision so it sticks. **What decision are you making?** Frame it as a clear choice: - "Should we build feature X in-house or integrate with Partner Y?" - "Should we launch with A/B test or full rollout?" - "Should we prioritize mobile app or web improvements in Q2?" **Why does this decision matter?** - What's the impact if we get it right? - What's the cost if we get it wrong? - Who else needs to be involved? **What's your timeline?** - When do you need to decide? - What forces the decision? (deadline, customer commitment, etc.) - What happens if we delay? Tell me about the decision and I'll help structure the document. ``` #