decide

# Decision Mode **Recommended model tier:** smart (opus) - this skill requires complex reasoning Formal decision-making workflow for architectural and technical choices. ## Purpose When facing a significant technical decision, this workflow guides you through structured analysis to make an informed choice that will be recorded and respected by all future sessions and agents. ## Workflow ### Phase 1: IDENTIFY Ask the user to clarify: - What decision needs to be made? - What is the context? (new system, migration, constraint?) - What are the requirements? (scale, team, timeline?) - Are there any hard constraints? **Example questions:** - "What technical decision do you need to make?" - "What problem are you trying to solve?" - "Are there any constraints I should know about?" ### Phase 2: EXPLORE Research and propose options: - List 3-5 viable alternatives - Include the obvious choices AND less common ones - For each option, note what it's best suited for **Output format:** ```markdown ## Options 1. **[Option A]** - Brief description - Best for: [use case] 2. **[Option B]** - Brief description - Best for: [use case] 3. **[Option C]** - Brief description - Best for: [use case] ``` ### Phase 3: ANALYZE For each option, evaluate: - **Pros**: What are the benefits? - **Cons**: What are the drawbacks? - **Fit**: How well does it match the requirements? **Output format:** ```markdown ## Analysis | Option | Pros | Cons | Fit ...