research

# Research Source-backed research for documentation, API migration, paper, or state-of-the-art questions. ## Input Schema ```json { "question": "required research question", "mode": "docs|sota|paper|methodology|code-fidelity", "constraints": [ "optional codebase, compute, version, or implementation constraints" ], "done_when": "recommendations are source-backed with caveats and confidence" } ``` ## Workflow ### 01: Create run directory Run `python PLUGIN_ROOT/shared/create_run.py --skill research` once. Retain its single printed path as `<run-directory>` and substitute that literal path into every later artifact path and helper argument. Never store or reuse the path through a shell variable; shell variables do not persist across tool calls. ### 02: Define research question, mode, and constraints Modes: - `docs`: current API/docs/migration answer. - `sota`: method comparison and implementation recommendation. - `paper`: single-paper analysis. - `methodology`: experiment design, metric, guard, and ablation review. - `code-fidelity`: compare paper/spec claims against implementation. ### 03: Gather sources Write `<run-directory>/sources.md`: ```markdown | Source | Type | Date/version | Why reliable | Used for | | --- | --- | --- | --- | --- | ``` Source rules: - Prefer primary docs, papers, specs, release notes, code. - Use current live sources for volatile docs, dependencies, APIs. - Mark stale/unavailable source explicitly. - Do not cite secondary s...