Research planning
Skill Amey-Thakur/AI-SKILLS/skills/research/research-planning
Scope a research question, decide what evidence would answer it, and plan the search before diving in. Use when starting any research task, so effort goes to the questions that matter instead of wandering.From its SKILL.md
npx -y skills add Amey-Thakur/AI-SKILLS --skill research-planningAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.9 KB, 621 tokens by cl100k_base, as published. Nobody here has run it
Research planning
Research that starts with "let me look into this" wanders, collects tangents, and stops when tired rather than when answered. Planning first (what exactly am I answering, what would answer it, where would I find it) turns research from a random walk into a directed search.
Method
- Sharpen the question until it is answerable. "Is X good?" is unanswerable; "Does X reduce Y for users like Z, at what cost?" can be researched. State precisely what you need to know and, crucially, what decision the answer informs: the decision bounds the depth and tells you when you have enough (see hypothesis-driven-work).
- Define what evidence would settle it. Before searching, decide what a convincing answer looks like: what facts, data, or sources would move you, and what would change your mind. This prevents motivated searching (collecting only what confirms a hunch) and tells you what to look for (see the falsifiability ethic in hypothesis-driven-work).
- Decompose into sub-questions. Break the main question into the pieces you can actually look up, ordered so early answers shape later searches. A complex question is a tree of answerable ones; research the tree, not the vague whole (see agent-task-breakdown for the analogous decomposition).
- Plan the sources by type. Match each sub-question to where its answer lives: primary sources (papers, docs, data) for facts, practitioners for experience, multiple independent sources for contested claims (see source-evaluation, literature-review). Know which questions need authoritative sources versus a quick lookup.
- Set a depth budget and a stopping rule. Decide up front how deep this warrants (a quick check vs a deep dive) and when to stop: typically when new sources stop changing the answer (saturation) or the decision is adequately supported. Research expands to fill available time without a stopping rule (see the time-box in root-cause-analysis).
- Stay open to reframing. If early findings show the question was wrong or the real issue is elsewhere, update the plan rather than grinding through the original one. Good research often changes its own question; hold the plan firmly but not rigidly.
Boundaries
- Planning is proportional to stakes: a quick fact needs no plan; a decision-shaping investigation does. Do not over-plan a five-minute lookup.
- A plan is a starting hypothesis about how to find the answer, not a script; the search will reveal better paths (see deep-research's iterative loop).
- Planning what to research does not evaluate what you find; that is source-evaluation and fact-checking, applied to every result.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.