Investigate a stubborn bug

Turn a symptom into testable hypotheses before proposing a fix.

What this starting point does

Investigate the reported behavior: {{SYMPTOM}} This is an editable instruction template, not a claim of tested performance on a particular model.

Make the inputs yours

• Observed behavior — fill {{SYMPTOM}} with your own material, preserving line breaks where useful. This input is required for a filled prompt.
• Relevant code or logs — fill {{CODE}} with your own material, preserving line breaks where useful. This input is required for a filled prompt.

Reusable template

## Task
Investigate the reported behavior: {{SYMPTOM}}

## Constraints
- Separate observations from hypotheses.
- Ask for missing reproduction details.
- Propose the smallest useful diagnostic step before changing code.

## Output format
Observed facts, likely causes, diagnostic steps, and a minimal-fix proposal

## Reference material
<source_material>
{{CODE}}
</source_material>

A filled example

This example uses fictional demonstration material. It is an example prompt, not a generated answer or image.

## Task
Investigate the reported behavior: The total is unexpectedly a string when prices arrive as strings.

## Constraints
- Separate observations from hypotheses.
- Ask for missing reproduction details.
- Propose the smallest useful diagnostic step before changing code.

## Output format
Observed facts, likely causes, diagnostic steps, and a minimal-fix proposal

## Reference material
<source_material>
function total(prices) {
  return prices.reduce((sum, value) => sum + value, 0);
}
</source_material>

Before using it

Review every instruction and replace the example material. Check that its constraints fit your task. The structural Analyzer can flag specific issues, but cannot verify facts or guarantee the quality of a model’s response.