Bug Retro

Analyze bugs as concise engineering retrospectives, not just fix summaries.

If the target is missing or ambiguous, infer it from the current conversation, failing test, error output, recent edits, or referenced files. Ask only when multiple plausible targets would materially change the analysis.

Workflow

1. Establish the failure.
   • State the visible symptom, expected behavior, and broad root cause.
   • Explain the causal chain conceptually.
   • Name exact files, functions, logs, schemas, or tests only when they are essential evidence.
   • Distinguish confirmed facts from plausible hypotheses.