Add 20 engineering/productivity skills from mattpocock/skills: ask-matt, code-review, codebase-design, diagnosing-bugs, domain-modeling, grill-me, grill-with-docs, grilling, handoff, implement, improve-codebase-architecture, prototype, research, setup-matt-pocock-skills, tdd, teach, to-issues, to-prd, triage, writing-great-skills. Update skills-lock.json with corresponding source/hash entries.
799 B
799 B
name, description
| name | description |
|---|---|
| research | 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. |
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.