research
by Matt Pocock · mattpocock/skills
Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
What it tells an agent to do.
The author’s own instructions, as your agent receives them — the same bytes the endpoint serves.
Spin up a background agent to do the research, so you keep working while it reads.
Its job:
- Investigate the question against primary sources (official docs, source code, specs, first-party APIs), not a secondary write-up of them. Follow every claim back to the source that owns it.
- Write the findings to a single Markdown file, citing each claim's source.
- Save it where the repo already keeps such notes; match the existing convention, and if there is none, put it somewhere sensible and say where.
More in planning & specs
brainstorming
Jesse Vincent
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirem…
What it does →writing-plans
Jesse Vincent
Use when you have a spec or requirements for a multi-step task, before touching code
What it does →executing-plans
Jesse Vincent
Use when you have a written implementation plan to execute in a separate session with review checkpoints
What it does →idea-refine
Addy Osmani
Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress…
What it does →interview-me
Addy Osmani
Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence …
What it does →planning-and-task-breakdown
Addy Osmani
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large …
What it does →