research-playbook

To investigate an unfamiliar codebase, apply a structured research workflow that guides you through framing questions, broad discovery, targeted deep-dives, and synthesizing findings into a clear report.

To debug elusive bugs, follow a five-phase research workflow: frame the issue, perform broad discovery, execute targeted deep-dives, cross-reference sources, and synthesize the findings.

Researching technical questions requires gathering context with grep, glob, file viewers, and web fetch, then moving through framing, discovery, deep-dive, cross-reference, and synthesis phases.

This codebase investigation workflow requires no external dependencies, relying entirely on common host tools like grep, glob, file viewers, web fetch, and code search to gather evidence.

You need a structured playbook for codebase investigations when onboarding new projects, diagnosing elusive issues, or answering technical questions that require multi-source evidence and synthesis.

Yes, you can use this research workflow for onboarding new codebases by framing questions, performing broad discovery, and executing targeted deep-dives to synthesize a structured technical report.