Debugging Strategy Exploration

D

Daniel Okoye

@daniel-okoye

·

Explore multiple debugging hypotheses to find the root cause.

1 copies0 forks
Explore debugging hypotheses for this issue.

Problem description:
{{problem}}

Symptoms: {{symptoms}}
Recent changes: {{recent_changes}}

## HYPOTHESIS 1: Infrastructure Issue
- Could this be a network, capacity, or resource issue?
- Evidence for: [list supporting evidence]
- Evidence against: [list contradicting evidence]
- Tests to validate: [list diagnostic steps]
- Likelihood: [low/medium/high]

## HYPOTHESIS 2: Code Bug
- Could this be a logic error or regression?
- Evidence for: [list supporting evidence]
- Evidence against: [list contradicting evidence]
- Tests to validate: [list diagnostic steps]
- Likelihood: [low/medium/high]

## HYPOTHESIS 3: Data Issue
- Could this be corrupt or unexpected data?
- Evidence for: [list supporting evidence]
- Evidence against: [list contradicting evidence]
- Tests to validate: [list diagnostic steps]
- Likelihood: [low/medium/high]

## HYPOTHESIS 4: External Dependency
- Could a third-party service be the cause?
- Evidence for: [list supporting evidence]
- Evidence against: [list contradicting evidence]
- Tests to validate: [list diagnostic steps]
- Likelihood: [low/medium/high]

## INVESTIGATION PLAN
- Prioritized order to test hypotheses
- Expected findings at each step

Details

Category

Coding

Use Cases

Complex bug investigationProduction issue debuggingSystematic troubleshooting

Works Best With

claude-opus-4.5gpt-5.2gemini-2.0-flash
Created Updated Shared

Create your own prompt vault and start sharing

Debugging Strategy Exploration | Promptsy