/research

name: research
description: 'Trace code or test a recurring pattern to answer one cited question. Use when: uncertainty needs evidence. Not for external feature teardowns; use reverse-engineer.'
practices:
- pragmatic-programmer
- ddd-bounded-context
hexagonal_role: driving-adapter
consumes:
- research-question
produces:
- research-report
- codebase-recon.v1
- pattern-mining.v1
context_rel: []
skill_api_version: 1
user-invocable: true
allowed-tools: Read, Grep, Glob, Bash, Write
metadata:
  capabilities: [research, codebase_recon, pattern_mining]
  effects: [write_research_report, write_recon_pack, write_pattern_evidence]
  canonical_status: canonical
  disposition: keep_specialist
  tier: execution
  dependencies: []
context:
  window: fork
  intent:
    mode: task
  sections:
    exclude:
    - HISTORY
output_contract: cited answer; findings.json for ordinary durable reports; validated codebase-recon.v1 or pattern-mining.v1 for selected evidence modes

Research

Answer the caller's bounded question with cited evidence. Choose ordinary investigation, repository tracing or pattern evidence according to the question; these are optional modes, not a sequence. A quick answer needs no report file.

Investigation

1. State the question and the decision it informs. Reuse the accepted scope and identify what evidence would answer it; do not expand the objective mid-search. 2. Inspect the smallest relevant sources. For changing external facts, use current primary sources. Verify search hits against the actual source. 3. Distinguish observation, inference, contradiction and unknown. Every material claim cites evidence; source agreement does not erase shared provenance. 4. Lead with the answer, then show evidence and remaining gaps. Each part of the question is answered or explicitly unknown with the searched scope disclosed.

Code claims cite the observed commit plus `file:line`. For uncommitted content, state HEAD and the changed-file status; do not claim the working bytes can be replayed from HEAD. Keep source identity and freshness visible. Search output, CASS, MS and prior reports are leads, not authority or required phases. Use the current agent by default; additional readers and runtimes require caller selection or existing authorization.

For several supplied reports, retain each source's identifier, author/runtime when known and revision/date. Compare claims as agreement, contradiction or unknown while preserving their original evidence. Repeated quotations of one upstream source are not independent corroboration. Verify decisive claims at their source and return one synthesis; do not launch recursive synthesis passes.

Repository tracing

For a repository model or audit, start from its declared entry points in docs, build manifests or command help and verify them against executable paths. Follow a relevant flow through entry, domain logic, integration and tests; prefer a completed trace to a shallow directory inventory. Report an interrupted trace at its exact file/line and explain what is missing. Choose a useful lens such as persistence, authorization, CLI, build or test without requiring a sweep of every lens.

An inline investigation may use dirty working-tree evidence with explicit limits. When a durable `codebase-recon.v1` pack is selected, its stricter contract applies:

• Write `codebase-recon.json` and a cited `codebase-recon.md` companion at the

caller's chosen location, default `.agents/scratch/codebase-recon/<run-id>/`. Keep mental model, bounded audit, pattern evidence and synthesis distinct.

• Bind the exact current full commit OID, at least one complete baseline flow,

claims with kind, confidence and evidence, and inspected/uninspected scope. Fact and inference citations resolve to repository-relative regular files at that commit; the companion report includes line references. Unknowns remain explicit.

• The manifest `report` names the companion and its lowercase SHA-256. The

companion has one `<!-- codebase-recon-report.v1 -->` marker and `manifest_commit`, `manifest_mode`, `flows_sha256`, `claims_sha256`, and `coverage_sha256` markers; section digests hash the `jq -cS` output for each section, including its trailing newline.

• Discover validated priors with

`skills/research/scripts/codebase-recon/validate-output.sh --repo-root <target> --discover-priors`. Prefer a verified delta when it answers the request. Delta evidence needs a valid ancestor chain, `baseline_verified: true` and the exact changed paths between the prior and current commits; do not relabel a directory scan as delta.

• Run `skills/research/scripts/codebase-recon/validate-output.sh --repo-root

<target> <recon.json>` before handoff. It checks both artifacts and rechecks their identities, HEAD and source state; dirty source outside `.agents/` cannot satisfy this commit-bound pack. Return a validation failure without disguising it as a completed recon pack.

Preserve earlier `.agents/recon/<run-id>/` packs and their exact cited identities. Prior discovery checks both legacy and current roots; never move or delete old proof to match a new layout. See the [recon scenarios](references/codebase-recon/codebase-recon.feature).

Pattern evidence

For a recurring implementation shape, test whether the similarity represents a reusable rule. Record replayable searches, examined hits and exclusions. Align independent implementations by their role in the behavior, then separate required invariants, legitimate variation and incidental syntax. Copies of one lineage do not count as independent evidence.

A `pattern-mining.v1` promotion needs at least three distinct anchored exemplars, a candidate formed before inspecting a separate holdout, a passing holdout and successful back-application of every refinement to the original exemplars. Every invariant needs supporting alignment. Otherwise preserve the result as `outcome: hypothesis` with `route: no-action`; do