| name | research-framework |
| description | Pre-edit investigation workflow for understanding code and behavior before changes. |
Research Framework
Mandatory before fixes, chained review remediation, performance changes, and standalone /code research.
Steps
- Scope affected path from request/error.
- Read target file(s) plus at least one caller or test.
- Trace data/control flow.
- State current behavior in 2-3 sentences.
- Form a
file:line hypothesis.
- Validate hypothesis before editing.
Rules
- No file edits during research.
- Say when tests are absent.
- If scope spans more than 3 files, list them before deep reading.
- Output behavior, dependencies, coverage, risks.