Menü
Generate and filter ideas into vetted options
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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-ideate |
| description | Generate and filter ideas into vetted options |
Follow these steps:
Decompose the opportunity, then establish:
Announce constraints — they become the step 4 filter.
Generate 15–25 raw ideas without evaluating. Quantity over quality. Work through:
Present as a numbered list with one-line descriptions.
Group ideas by underlying pattern — shared mechanism, same part of the problem, similar resources, or variations of each other. Reduce to 4–6 named clusters, each a distinct strategic direction.
Check each cluster against the hard constraints: timeline, resources, technical viability, organizational fit. Be ruthless — don't soften constraints to save appealing ideas. Mark each: Feasible / Conditional (needs X) / Eliminated (fails Y).
For each surviving cluster: select the strongest variant, sketch how it works, identify the key risk, and note what makes it distinct. Enough detail to compare, not full plans.
Present 2–5 refined options:
**Option [N]: [Name]**
- Approach: [one sentence]
- Strengths: [what it does well]
- Key risk: [main thing that could go wrong]
- Requires: [key dependencies]
Suggest next steps: clear trade-offs → weigh options; many factors → priority matrix; high stakes → premortem; stakeholder complexity → perspective shift.