research · git:20261116.18a1a15 · 2026-11-16 · sha256 af2e3ed2287a494c

research git:20261116.18a1a15A

Immutable. This exact content never changes and is served at /api/v1/blob/af2e3ed2287a494c.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_3uunlm4nfyu7t4l3/af2e3ed2287a494cd97011f2657e303b695163e175c4e16dde24f4d49ea477ff.json

Then /plugin install research@markdownregistry-3uunlm4nfyu7t4l3 in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: research
description: "Starts Phase 1 (Research) for a topic: reads every relevant file, optionally runs a panel of Explore teammates, and saves a research artifact to .claude/state/research/. Use when the user says 'research <topic>' or '/research', or before planning work in unfamiliar code. Research only - proposes no solutions."
---

Start Phase 1 (Research) for the following topic: $ARGUMENTS

Resolve `$STATE` first: `.claude/state` in the main checkout of the repo being changed, per `rules/state-persistence.md`.

For bigger topics, run **panel mode** (see `rules/parallel-agents.md`): spawn one `Explore` teammate per subsystem, run one bounded cross-check round via SendMessage so teammates flag contradictions across their areas, then pull their findings together into the artifact yourself. For narrow topics, explore solo. Read all relevant files, check git history for context, and investigate related patterns.

Save the research artifact to `$STATE/research/YYYY-MM-DD-research-<topic>.md` (use today's date) containing:

- **Findings**: what you discovered in the codebase
- **Open questions**: things that need clarification
- **Constraints**: technical or business limitations
- **Related code**: key files and functions involved

Do NOT propose solutions yet. Research only.