debug

A systematic debugging workflow guides you through diagnosing software defects by capturing error context, reproducing steps, collecting evidence, and verifying fixes using a structured checklist to identify root causes.

To start a debug session, describe the issue you are facing in one sentence and ask the assistant to start the workflow, which will then capture the error context and log the investigation progress.

During a reproducible debug session, logging works by writing investigation findings and progress to a `.planning/DEBUG-LOG.md` file, ensuring that all error context and evidence are tracked for future reference.

Yes, you can use this structured debugging workflow for CI environments, as it applies to error investigations across codebases and supports reproducible debug sessions in both development and CI contexts.

The best way to ensure a fix is reproducibly verified is to follow the structured debugging checklist to identify the root cause, apply the fix, and document the close session workflow after verification.

You need to track evidence when diagnosing software defects to maintain a structured record of error context and reproduction steps, which helps identify the root cause accurately and supports a documented close session workflow.