Raven Research

Follow working on GitHub tasks. Rebuild the local change and sources; a new report may create a folder without an issue/Project. Do not prepare a plan or implementation during research itself. Talk to the user in their language; write the report in the user's language unless the project already uses another.

1. Establish evidence and scope

• If the user mentions specific files (tickets, documents, JSON), read them first IN FULL (no limit/offset).
• CRITICAL: read those files yourself in the main context before launching any subtasks.

Read the PRD, relevant documentation, context/foundation/architecture.md and context/foundation/lessons.md if they exist, and treat lessons entries as already known patterns while shaping the research areas — recurring rules the team has accepted narrow what is worth re-investigating.

Keep a concise list of questions to answer, existing evidence, unresolved contradictions and next checks. A focused question may need a single local lookup; a comprehensive scope by default needs coverage of every agreed area, delegated in parallel (step 2).

Clarify only an ambiguity that would materially change the investigation, with the AskUserQuestion tool: short headers (max 12 characters) and concrete options with descriptions. An unambiguous research request needs no interview. User preferences are decisions; verify corrected factual claims against the given source.

2. Choose and run the investigation

Work locally for a single located fact or sequential reasoning. Comprehensive or multi-area research is delegated by default, not as an exception. Before the first delegation read references/task-orchestration.md and use its bounded assignments, capability checks, failure fallback and evidence requirements. Launch subagents in parallel in one message only for independent gaps you can use right away (usually 1–2, at most 4), each for a different research dimension and each asked for file:line anchors — for example one finding every file related to X, one looking for earlier decisions about Y in documents and Git, one analyzing how subsystem Z works. Delegate less only when the scope really concerns one area or a gap depends on a prerequisite that is still unsettled. Use Explore subagents for locating code and general-purpose for analysis. Use task tracking when it helps coordinate several areas; otherwise a working list is enough.