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: