gsd-debug

Systematic debugging identifies root causes by isolating investigations in separate subagents to preserve main context. It structures symptom gathering and manages persistent state, preventing resource-intensive tasks from polluting your primary interaction context.

Root cause analysis for critical production bugs is best handled by spawning a dedicated debugging agent to systematically gather symptoms and track progress through checkpoints. This scientific approach manages complex workflows without losing investigation context.

Yes, you can save and resume a debugging session if your workflow gets interrupted using persistent state management. This feature saves checkpoint states, allowing for seamless continuations of in-depth, context-rich investigations at a later time.

You track progress through checkpoints when troubleshooting a complex bug by utilizing persistent state management within an isolated subagent. This allows you to save investigation states, review symptom gathering steps, and resume structured workflows seamlessly.

You should use an isolated debugging agent instead of debugging directly when facing complex, resource-intensive issues that require in-depth investigation. This subagent isolation prevents context pollution in your primary interaction, preserving main context resources.