Skill 02 — Context Researcher (Probe-first)

Purpose: Collect the minimum sufficient repo + vault context for the current task, with evidence pointers.

Protocols:

• •[[docs/PROTOCOLS/VAULT_PROBE]]
• •[[docs/PROTOCOLS/EVIDENCE]]
• •[[docs/PROTOCOLS/RUN_LOGGING]]
• •[[docs/PROTOCOLS/PATCH_GATE]]
• •[[docs/PROTOCOLS/CONTEXT_BUDGET]]

Tools:

• •[[tools/repl/README]] — patch-gated edits (generate + check + apply)

Inputs (from Orchestrator)

• •Task slug + link to docs/tasks/<task_slug>.md (required)
• •Optional: scope hints (folders, components, endpoints)

Outputs (must write)

• •docs/research/<task_slug>.md
• •artifacts/research_findings.json
• •[[docs/skills/02_context_researcher/SUMMARY]]

Run log (mandatory)

Create: artifacts/_runs/<timestamp>_02_context_researcher/

Steps

1. •Read the task note with minimal slicing:
   • •use probe open or probe section
2. •Use probe to locate relevant areas:
   • •search across repo for key terms (component names, routes, KPIs, table names)
   • •use tree to confirm folder boundaries
3. •For each relevant area, open only small slices:
   • •entrypoint files
   • •relevant config
   • •the few most relevant functions/components
4. •Write docs/research/<task_slug>.md using docs/templates/RESEARCH_TEMPLATE.md as a guide.
5. •Write artifacts/research_findings.json with:
   • •task_slug
   • •key_files (array of paths)
   • •evidence (array of {path, from, to, why})
   • •open_questions (array)
   • •risks (array)
6. •Write SUMMARY.md with a short bullet list and links to outputs.

Definition of Done

• • Research note exists and is readable in Obsidian
• • Research includes evidence pointers for every key claim
• • Findings JSON exists and includes at least 5 evidence items (or fewer if repo is tiny, with explanation)