research
Investigate a question against high-trust primary sources and publish the assigned artifact, defaulting to a Markdown findings file in the repo. Use for topic research, docs or API facts, and delegated investigation, including triage research runs.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- research
- description
- Investigate a question against high-trust primary sources and publish the assigned artifact, defaulting to a Markdown findings file in the repo. Use for topic research, docs or API facts, and delegated investigation, including triage research runs.
02 资源文件 2
- 参考文档agents/openai.yaml94 B
- 参考文档CREDITS.md2.6 KB
03 SKILL.md 正文
A prompt or brief naming this skill is its invocation.
Perform the investigation in the current run, including when another run delegated it to you.
- 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.
- When the task assigns an artifact and destination, publish the findings there, citing each claim's source. For an assigned issue artifact, publication is complete on the issue; no repository findings file or index edit is needed. Post an issue or pull request artifact as
.repo-standards/rules/comments.md#disclaimerssays. - Otherwise, write the findings to a single Markdown file, citing each claim's source. Save it where the repo's documentation rules or existing convention put such notes, such as beside the usage or development topic it serves, and add it to that directory's index, creating the index when those rules require one. If there is no such place, put it somewhere sensible and say where.
Reads
Paths are relative to the repository root.
- The installed documentation rules, which the
repository-standardsskill looks up. When they are missing, follow the repository's existing convention for such notes, or put them somewhere sensible and say where, as step 3 says. - The index of the directory the notes go in, such as
docs/development/README.md. When it is missing, create it only when the documentation rules require one. .repo-standards/rules/comments.md: the installed comment rules, whose section the posting steps name. When it is missing, post issue bodies and comments as the steps describe.
04 同仓库更多 Skills
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
triage
Move issues and external PRs through a state machine of triage roles, sort each request by where its uncertainty lies, and bring its agent brief to acceptance through research and independent review, or through a grilling session with the owner. Also runs unattended as the factory's triage run, which writes nothing and ends with a run result.
to-tickets
Break a specification into independently mergeable tickets, publish them in their responsible repositories with native parent and blocking links, and return the split for independent review.
to-spec
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
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.