radarist/structured-analytic-skills / skills/decompose-research-question
decompose-research-question
VerifiedBreaks a question too large, vague or multi-part to answer directly into a MECE issue tree of atomic sub-questions — each mapped to the skill or research step that answers it, ordered by dependency, with a named method for recombining the answers. Use when a request would otherwise sprawl — "help me understand the whole X landscape", "what's the future of Y and is it worth investing in?", "decompose this research question", "break this big question into parts before researching". Not for structuring an answer already in hand — use `pyramid-principle`; not for a single factual lookup — use `grounded-answer`.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.9 KB |
| agents/openai.yaml | config | 385 B |
| evals/evals.json | config | 4.7 KB |
agents/openai.yaml
View on GitHub# Generated by evaluation/build_openai_metadata.py — do not edit by hand.
interface:
display_name: "Decompose Research Question"
short_description: "Breaks a question too large, vague or multi-part to answer directly into a MECE issue tree of atomic sub-questions"
default_prompt: "Use $decompose-research-question to apply Issue-tree decomposition to the material I provide."
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |