research-framework

name	research-framework
description	Pre-edit investigation workflow for understanding code and behavior before changes.

Research Framework

Mandatory investigation before proposing or implementing changes.

When Required

• Before ANY code fix (runtime, lint, type errors)
• Before implementing review findings (--chain)
• Before performance changes
• Standalone via /code research

Steps

1. Scope: Identify affected code path from error/request
2. Read: Target file(s) AND at least one caller or test
3. Trace: Follow data/control flow through affected path
4. Understand: State current behavior in 2-3 sentences
5. Hypothesis: Propose what's wrong with file:line evidence
6. Validate: Check hypothesis against tests/runtime before editing

Rules

• Do NOT edit files during research
• If no tests exist, say so explicitly
• If path spans >3 files, list all before diving in
• Output stays in conversation context, not written to files

Standalone Output

## Research: {scope}

### Files Examined
- {file:line — role}

### Current Behavior
{2-3 sentences}

### Dependencies
- {upstream}: {how it feeds in}
- {downstream}: {what depends on it}

### Test Coverage
- {test file}: {coverage}
- **Gaps**: {untested paths}

### Risk Assessment
- {what could break}