Multi-Path Debug

Use this skill when the user reports a bug, regression, runtime failure, incorrect behavior, flaky test, broken workflow, or production symptom and the next responsible step is root-cause confirmation rather than immediate repair.

The purpose is to split debugging into two explicit phases:

1. Root-cause investigation and user confirmation.
2. Fix implementation only after the user confirms the root-cause summary and authorizes repair.

Do not combine those phases. Never edit code, config, migrations, tests, or runtime behavior while this skill is still in the root-cause phase unless the user explicitly authorizes a narrow diagnostic-only change.

For concrete conversation fixtures, read references/interaction-fixtures.md when modifying or auditing this skill.