Loading...
Loading...
Found 116 Skills
Apply a latticework of mental models from multiple disciplines to improve decision quality. Use this skill when the user needs to think more clearly, avoid cognitive blind spots, apply cross-disciplinary reasoning, or evaluate a complex decision from multiple angles — even if they say 'how should I think about this', 'what am I missing', 'give me a different perspective', or 'what frameworks apply here'.
Use logic tree approach to identify root causes of business problems. Use when diagnosing performance issues, process failures, or customer behavior patterns.
Root-cause-driven solution decision framework for the hardest problems across any domain. This is the nuclear option — it consumes significant tokens through exhaustive multi-branch root cause analysis, MECE solution enumeration, and domain-adaptive external validation. Use ONLY for genuinely difficult problems: recurring failures that resist repeated fix attempts, complex systemic issues with no clear solution path, decisions where multiple approaches exist and the wrong choice has high cost, problems with multiple interacting causes spanning components or teams. Trigger when: the user says 'what's the best way to fix X', 'why does this keep happening', 'how should we approach this', 'find the root cause', 'what are my options for fixing X', 'analyze this problem systematically', 'evaluate our options for X', 'what's the right approach and why', or expresses frustration that previous solutions didn't stick. Do NOT use for: problems where the answer is already obvious or requires no analysis, straightforward issues with clear solutions, or routine investigation. If the problem can be solved in 5 minutes of investigation, this skill is overkill.
Iterative Five Whys root cause analysis drilling from symptoms to fundamentals
When a user is stuck, frustrated, or describing a problem vaguely, do NOT immediately suggest solutions. First, force structured problem articulation through targeted questions: What did you expect? What happened instead? What have you tried? Only after the problem is clearly defined, propose solutions.
Execute tasks through systematic exploration, pruning, and expansion using Tree of Thoughts methodology with multi-agent evaluation
Define your Method — the unique methodology you use to deliver your transformation. This is the third element of the World Code framework. Use when someone says "define my method", "my methodology", "how I solve problems", "unique approach", or "method element".
Apply first principles thinking to break problems down to fundamental truths and reason up from there. Use this skill when the user is stuck in conventional thinking, needs to challenge assumptions, find breakthrough solutions, or evaluate whether something is truly impossible vs just assumed to be — even if they say 'everyone does it this way', 'is there a fundamentally better approach', 'why does it have to cost this much', or 'challenge my assumptions'.
Iterative PDCA cycle for systematic experimentation and continuous improvement
Use after 2 consecutive failed attempts at solving a problem - STOP guessing and research documentation, codebase, and online resources before resuming
Systematic Fishbone analysis exploring problem causes across six categories
Sequential Thinking MCP and UltraThink mode for deep analysis, complex problem decomposition, and structured reasoning workflows. Use when performing multi-step analysis, architecture decisions, technology selection trade-offs, breaking change assessment, or when --ultrathink flag is specified. Do NOT use for simple decisions or straightforward implementation tasks.