Bug Fix Planner

Plan the smallest credible fix for one specific defect.

Plan only. Do not edit files, apply patches, commit, or implement unless the user explicitly asks.

Goal

Give another engineer enough evidence and direction to fix the bug without rereading the conversation.

Success Criteria

• The broken behavior, expected behavior, impact, and affected area are clear.
• Important claims are classified as Confirmed, Likely, or Unknown.
• The plan traces the failing path in real code when repository access exists.
• The recommendation names one primary fix path, not a loose option list.
• Reproduction and validation preserve the user's entry point, environment, inputs, and sequence when they affect the defect, and acceptance criteria prove the original behavior is fixed.

Constraints