Menu
Adaptive multi-phase reasoning for complex problems
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Break a whole into parts at its natural joints
Tile the space of possible futures and evaluate strategies across the tiles. Blends part-whole decomposition with tree and graph of thought. This skill should be used when the user asks "what if", "what could happen if", "evaluate possible futures", "map the scenarios", "explore how this could play out", "compare futures", "stress-test this plan against the future", or faces a decision whose outcome hinges on unresolved uncertainties. Ends with a single reasoned recommendation plus the conditions that would flip it.
Distributed navigation system for multi-file pipelines and processes. Creates compact, grep-friendly waypoint markers that orient readers within complex cross-file workflows — each file carries its own ID, role, adjacent nodes, and a pointer to the full map. Use when asked to "point me to", "where does X begin/end", "map this pipeline", "add waypoints", "trace this process", or when working with processes spanning many files that need discoverability without centralized documentation that drifts.
Ask a genuinely good question — or a composed set of them — in the moment, to discover, clarify, probe, or confirm, in any conversation or domain. Use when about to ask the user something or use the `AskUserQuestion` tool, when a question fell flat or one won't reach and you need a set, when the user's tone or messages signal you have drifted from what they need, or when the user wants questions phrased, generated, or sharpened — "read this spec and generate questions", "ask about the schema", "review this and ask questions", "help me understand what to ask", or to clarify a requirement or idea.
Communicate ideas and information to others with purpose, clarity, and integrity. Ensure that artifacts are structured and phrased in a way that is mindful of their audience while avoiding AI slop patterns. Use when the user requests assistance with writing, commentary, or communication; when they point out AI slop, when they ask things like "help me say", "write for [a specific audience or context]", "polish [comments, sentences, artifacts]", or the like.
Visualize data, concepts, relations, or diagrams. Produces browser-runnable HTML charts and markdown outputs that drop into pull requests, READMEs, tickets, and chat. Use whenever the user asks to visualize anything, make a chart or diagram, plot a trend, compare numbers, show a flow or timeline, or pick the right chart type.
| name | thinkies-strategize |
| description | Adaptive multi-phase reasoning for complex problems |
Follow these steps:
Target: $ARGUMENTS, else ask for clarification. Choose a descriptive working name (e.g. "api-architecture-exploration") so later turns can reference it. Tell the user: "Working on: [name]". Go to step 2.
Repeat until the user signals done.
3a. Apply structured reasoning to the current aspect. Select and chain techniques: argument standardization, fallacy detection, evidence evaluation, assumption surfacing, contrapositive testing, defeater hunting. Present findings as prose woven into the dialogue.
3b. Await user response.
3c. Route on the response:
Summarize what was explored and concluded. Surface transferable insight worth keeping beyond this session. Identify what remains unresolved and what a successor exploration would address.
