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
Get the questions. From the user, or from a questions file they name. Read any file they mention in full before anything else.
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.
Split the questions into areas and research them in parallel with
Exploreagents (two to six, grouped by area, not one per question). Ask each forfile:lineevidence.Check the agents' claims that the document will rest on: open the cited lines yourself. An agent's summary is a claim, not evidence.
Write the body to a scratch file using references/research-template.md, then create the artifact:
node "${CLAUDE_SKILL_DIR}/scripts/artifact.mjs" create \ --task <task> --kind research --slug <slug> --title "<question>" --author <your seat> --body /tmp/research-body.md # prints .ork/tasks/<task>/NN-research-<slug>.mdReply 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:lineor 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-researchrevises it from comments./ork:create-planreads it next.
