Research
Two halves, in this order: the documents of record for this project, then
prior art outside it. Answering from memory and calling it research is the
thing this skill is here to stop.
Match the shape of the ask:
- A question ("is this possible", "are we doing this right", "don't touch
code"): look it up, report, stop. No edits until told to go (→
audit-only).
- Part of the work ("research and fix", "sleuth GitHub and iterate until
it's right"): research inside the loop. Look, apply, re-check, and say what
each pass was based on — don't halt the loop to file a report.
Pick a depth and say it
| Depth |
For |
Shape |
| quick |
one fact, one API, one flag |
a source or two, answer in a paragraph |
| medium |
"how do people do this", choosing an approach |
3-6 sources, compare, recommend |
| very thorough |
architecture, redesign, "this has to be solved somewhere" |
survey the field, name the canon, ROI-ordered options |
Fan out with parallel subagents for breadth. Give each one a scope, a
Thoroughness: level, Do not edit files., and a return contract: exact paths
with line numbers and short quotes for code, or URL, technique, license, and
applicability for outside repos.
Documents of record first
Exhaust what the project already states before searching the web.
- Tickets and specs: the tracker issue, the PRD or spec, QA feedback, the Slack
or Discord thread that started it — whatever this project treats as the
record.
- The repo's own planning docs:
plans/, docs/, ADRs, AGENTS.md,
CONTEXT.md, README.
- Figma dev mode when the question is visual. The design is the source of truth
(→
ui-system).
- The repo itself:
git log -S<symbol> and git log -p for why the code got
this way, and the vendored source in node_modules or site-packages instead
of a remembered API surface.
When two documents disagree, say so instead of silently picking one. "Double
check against X, Y, Z" means re-read each one and answer per document, not
re-skim your own diff.
Then prior art
Someone has almost certainly solved this. Go find them and take it.
- GitHub:
gh search repos, gh search code, gh api. Read the real source,
not the README. Note the license before recommending a lift.
- arXiv and papers for anything on agents, generation, simulation, scheduling,
or scoring.
- Vendor docs and changelogs for API truth. Tutorials, blogs, Reddit, HN, and
YouTube for what people actually hit in practice.
Report what is reusable, which pattern to copy, and what to leave behind.
Grade the evidence
Rank the sources and mark which tier a claim sits in:
- Vendor-documented, or the shipping source code. Strongest.
- Maintainer statements, papers, primary repos.
- Blogs, tutorials, forum posts, model memory. Weakest, flag them as such.
Every non-obvious claim carries a URL. With no URL, write "unverified" rather
than stating it flat.
Don't
- Answer from memory and call it research. "Are you sure?" and "did you
research?" mean you already got caught doing it.
- Call something impossible or unsupported without opening the docs or source.
- Stop at the first hit when the question was "how do people do this".
- Hand back a link dump. The deliverable is the recommendation, with the
sources under it.
- Drop the research on the floor. When it drives a change, the PR description
carries what was found and why (→
pr-update). When it's a big survey with
no PR yet, write it into the repo's planning docs so it outlives the chat.
1---2name: research3description: Look it up before answering or building — this project's documents of record first, then external prior art. Use when the user says research, look it up, sleuth GitHub, "what do other people do", "is that a thing", "are you sure", or asks for something that has obviously been solved before.4---56# Research78Two halves, in this order: the **documents of record** for this project, then9**prior art** outside it. Answering from memory and calling it research is the10thing this skill is here to stop.1112Match the shape of the ask:1314- **A question** ("is this possible", "are we doing this right", "don't touch15 code"): look it up, report, stop. No edits until told to go (→ `audit-only`).16- **Part of the work** ("research and fix", "sleuth GitHub and iterate until17 it's right"): research inside the loop. Look, apply, re-check, and say what18 each pass was based on — don't halt the loop to file a report.1920## Pick a depth and say it2122| Depth | For | Shape |23|---|---|---|24| quick | one fact, one API, one flag | a source or two, answer in a paragraph |25| medium | "how do people do this", choosing an approach | 3-6 sources, compare, recommend |26| very thorough | architecture, redesign, "this has to be solved somewhere" | survey the field, name the canon, ROI-ordered options |2728Fan out with parallel subagents for breadth. Give each one a scope, a29`Thoroughness:` level, `Do not edit files.`, and a return contract: exact paths30with line numbers and short quotes for code, or URL, technique, license, and31applicability for outside repos.3233## Documents of record first3435Exhaust what the project already states before searching the web.3637- Tickets and specs: the tracker issue, the PRD or spec, QA feedback, the Slack38 or Discord thread that started it — whatever this project treats as the39 record.40- The repo's own planning docs: `plans/`, `docs/`, ADRs, `AGENTS.md`,41 `CONTEXT.md`, README.42- Figma dev mode when the question is visual. The design is the source of truth43 (→ `ui-system`).44- The repo itself: `git log -S<symbol>` and `git log -p` for why the code got45 this way, and the vendored source in `node_modules` or site-packages instead46 of a remembered API surface.4748When two documents disagree, say so instead of silently picking one. "Double49check against X, Y, Z" means re-read each one and answer per document, not50re-skim your own diff.5152## Then prior art5354Someone has almost certainly solved this. Go find them and take it.5556- GitHub: `gh search repos`, `gh search code`, `gh api`. Read the real source,57 not the README. Note the license before recommending a lift.58- arXiv and papers for anything on agents, generation, simulation, scheduling,59 or scoring.60- Vendor docs and changelogs for API truth. Tutorials, blogs, Reddit, HN, and61 YouTube for what people actually hit in practice.6263Report what is reusable, which pattern to copy, and what to leave behind.6465## Grade the evidence6667Rank the sources and mark which tier a claim sits in:68691. Vendor-documented, or the shipping source code. Strongest.702. Maintainer statements, papers, primary repos.713. Blogs, tutorials, forum posts, model memory. Weakest, flag them as such.7273Every non-obvious claim carries a URL. With no URL, write "unverified" rather74than stating it flat.7576## Don't7778- Answer from memory and call it research. "Are you sure?" and "did you79 research?" mean you already got caught doing it.80- Call something impossible or unsupported without opening the docs or source.81- Stop at the first hit when the question was "how do people do this".82- Hand back a link dump. The deliverable is the recommendation, with the83 sources under it.84- Drop the research on the floor. When it drives a change, the PR description85 carries what was found and why (→ `pr-update`). When it's a big survey with86 no PR yet, write it into the repo's planning docs so it outlives the chat.
outthislife