Investigation Workflow

This is a structured 6-phase workflow for investigating existing codebases when you need to actually understand how something works before changing it. It's normally invoked automatically by dev-orchestrator, but you can run it standalone via the recipe runner. The workflow goes from scope definition through parallel deep dives (multiple agents exploring simultaneously) to verification and knowledge capture. What's notable is the emphasis on not reading the markdown docs and following phases manually. The recipe runner enforces the actual phase ordering and agent deployment. Use this when you're asking "how does authentication work" or "why is CI failing," not when you're ready to implement something.