Investigate and clarify a reusable codebase topic through dialogue, then create or update a `.memory-bank/research` note only after explicit human confirmation.
Installs into .claude/skills of the current project.
Are you the author of Research Scope?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/blockscout-research-scope-7fa87e8f)
---
name: research-scope
description: Investigate and clarify a reusable codebase topic through dialogue, then create or update a `.memory-bank/research` note only after explicit human confirmation.
---
# Research Scope
Use for durable research into a subsystem, runtime flow, integration boundary, or architectural slice.
Follow `../../../.memory-bank/workflows/research-scope.md`.
Start with the relevant material from `../../../.memory-bank/README.md`, `projectbrief.md`, `sync-architecture.md`, `operation-lifecycle.md`, `api-surface.md`, `gotchas-and-edge-cases.md`, and existing research notes. Treat code, config, schemas, and tests as source of truth.
Do not create or update a research note without explicit `write result` / `update result`-style confirmation. Discuss a strong overlap with an existing note before choosing its persistence target.
