strategic-investigation

Debugging strategy becomes essential after 1-2 failed attempts, when errors remain unclear, multiple valid approaches exist, or quick hacks are tempting. Plan-driven investigation with parallel exploration surfaces idiomatic solutions faster than repeated variations.

Acknowledge being stuck, enter plan mode to structure investigation, spawn 2-4 Explore agents in parallel with focused questions on different angles, collect their findings with file paths and code snippets, then synthesize an idiomatic solution aligned with framework conventions.

Parallel exploration with subagents investigates different approaches simultaneously, surfacing concrete findings and trade-offs quickly. Sequential attempts risk spinning wheels on variations of the same failed approach; parallel investigation breaks that loop and finds framework-aligned solutions.

Yes. Parallel Explore agents are designed precisely for this: after standard approaches fail, they pursue different investigation angles concurrently, returning concrete findings with file paths and code snippets to identify the idiomatic solution.

If the synthesized solution from parallel agents fails, repeat the plan-mode cycle with refined questions or new investigation angles. Escalate if repeated cycles exhaust framework conventions or reveal structural constraints beyond the immediate problem scope.

Acknowledge being stuck and commit to a plan; have clear error context and attempted approaches documented; formulate 2-4 focused questions targeting different investigation angles; be ready to collect findings and synthesize them into an executable solution.