investigation-create

An investigation workflow is needed when a task requires exploratory analysis across multiple aspects or cross-session work; otherwise, a direct chunk workflow suffices for contained changes.

The best way to document an investigation overview is to seed a structured OVERVIEW.md file containing the Trigger, Success Criteria, and initial hypotheses to guide discovery.

Start an investigation by generating an investigation directory and seeding it with an OVERVIEW.md file that outlines initial hypotheses and potential chunks for structured discovery.

Cross-session exploration is needed for decision-making tasks when the work demands exploratory analysis across multiple systems or aspects that cannot be resolved in a single contained chunk workflow.

You can use a chunk workflow for ambiguous tasks if they do not require cross-session exploration or multi-aspect analysis, allowing for a quicker and more contained change process.

The limitation of using an investigation workflow for simple tasks is unnecessary overhead; straightforward tasks that lack multi-aspect exploratory analysis should be redirected to a chunk workflow.