thinking-method-selector

Topics in the source

• Thinking Method Selector
• When to use
• How to run
• Situation to method
• Fallback outlines
• Pitfalls
• Checklist

Match the user's situation to one thinking method, say why, and run it. Pick by what the user must decide or produce next, not by keywords. The user is stuck, torn or overwhelmed and has not said how they want to think about it. A problem is stated loosely and several methods could apply. The user asks "which framework should I use?". Skip: execution tasks (write, fix, build), plain factual questions, or any request that already names a method (use that method). 1. Restate the situation in one line, including the decision or output the user needs next. 2. Gather first. If you can read the repo, docs or data that frame the problem, do it before choosing. Ask at most one question, only if two methods fit equally and the answer would change the pick. 3. Choose one method from the table below. Say in one sentence why it fits and why the nearest alternative does not. 4. Run it. If the named skill is installed, follow its instructions. If it is not, use the matching outline under "Fallback outlines" and say which method you are using. 5. Offer at most one follow-on method (for example "after the pre-mortem, a tradeoff analysis would settle which option"). | The user needs to... | Method

This is an excerpt. Refer to the complete source and its current requirements.