Agent skill · yonatangross
create-research
Documents how code works today for a task's questions, with file:line citations. Use before planning a change; describes, never proposes. NOT for mapping a repo (use explore).
What it needs
About 1k tokens when loaded.
What this skill does
create-research Answer the task's questions about the code as it is, and save the answer as one research file. It is a map, not a proposal: no recommendations, no fixes, no critique. Layout: the create-plan skill's references/artifact-layout.md. Steps 1. Get the questions. From the user, or from a questions file they name. Read any file they mention in full before anything else. 2. Do not read the task's ticket or plans. Research describes the code; a ticket that wants a change biases it. Earlier research artifacts in the task directory may be read. 3. Split the questions into areas and research them in parallel with Explore agents (two to six, grouped by area, not one per question). Ask each for file:line evidence. 4. Check the agents' claims that the document will rest on: open the cited lines yourself. An agent's summary is a claim, not evidence. 5. Write the body to a scratch file using references/research-template.md, then create the artifact: 6. Reply with the path and the open questions, and stop. Rules Describe, never prescribe: no "should", no "we could", no diff blocks. Every finding cites path:line or a line range. Say when a list is complete and when it is a sample. Open questions are about what was not traced ("how does X reach Y?"), not about what to build. Related /ork:iterate-research revises it from comments. /ork:create-plan reads it next.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills yonatangross/create-research--4982e9