โ† ClaudeAtlas

better-thinkinglisted

๐Ÿง  Classify an incoming task by its shape (decision, diagnosis, research, creative, communication, learning, negotiation) and its stakes, then select which skills to deploy at what depth. Use as the first move on any nontrivial task, before any substantive work begins.
skyf0xx/better-thinking ยท โ˜… 3 ยท DevOps & Infrastructure ยท score 77
Install: claude install-skill skyf0xx/better-thinking
# Better Thinking Classify an incoming task by its shape and stakes, and select which skills to deploy at what depth โ€” the dispatcher that decides how much thinking machinery a task deserves. ## Why Applying full machinery to a trivial task wastes effort; applying none to a consequential one is negligent. A fast, explicit classification step routes effort proportionally before substantive work begins. ## Use when / Don't use when - **Use when:** at first contact with any nontrivial task โ€” the entry point other skills dispatch from. - **Don't use when:** never skip it; scale depth down instead โ€” triage on a small task takes seconds. ## Inputs โ†’ Outputs - **Inputs:** an incoming task, question, or request. - **Outputs:** a task classification (shape + stakes + reversibility) and a selected set of skills and depth. ## Principles - Classify by shape first โ€” decision, diagnosis, research question, creative generation, communication, learning, negotiation, or a combination. Shape determines which skill family is even relevant. - Classify by stakes and reversibility second. This determines depth, independent of shape. - A task can be routine in domain but high-stakes in consequence โ€” don't classify by surface topic or tone alone. - Resolve vague or underspecified language before routing โ€” routing a fuzzy restatement of the request just picks the wrong tool with more confidence. - Re-triage if the task's real shape differs once underway; the initial classification is a hypot