research
Investigate a specific technical question using primary sources and save a cited research note.
- License 许可
- MIT
- 最近更新
- 2026-09-16
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- research
- description
- Investigate a specific technical question using primary sources and save a cited research note.
02 资源文件 1
- 许可证LICENSE1.0 KB
03 SKILL.md 正文
Research a bounded question
Identify the decision this research supports, the deliverable, and any existing budget. Prefer official documentation, papers, source code, and first-party measurements. Distinguish reported results, your interpretation, and claims that still need testing in the user's environment.
For a narrow lookup, investigate directly. Delegate only when an independent question can run alongside useful local work and the host permits delegation. Give a worker its question, allowed resources, output path, and stopping rule. Delegated researchers perform the research themselves; they do not recursively invoke this skill to create more researchers. Honor the host's concurrency limit and the caller's resource budget. Never create user-visible tasks as a substitute for an internal worker without a user request.
Stop when the question is answered with adequate evidence, the agreed budget is reached, or a specific unavailable source blocks the conclusion. Do not expand into a general survey when the decision no longer needs it. Ask for a budget only when resource use is material and cannot be inferred; a small lookup needs none.
Save one concise Markdown note in the project's usual location, or at the path the user requested. Include the question, findings with supporting links, uncertainties, and the next decision. State source versions or dates when they matter. If a source is inaccessible, state that limitation rather than treating its title or an abstract as full verification.
04 同仓库更多 Skills
wayfinder
Map unresolved decisions for a large initiative and work through their dependencies until a plan is actionable.
to-tickets
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
to-spec
Turn an agreed feature or plan into a proportionate, testable specification at the requested destination.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
setup-matt-pocock-skills
Configure missing tracker and domain-document conventions for the Matt Pocock workflows in a repository.
research
Investigate a specific technical question using primary sources and save a cited research note.