fix-planner

You can generate an actionable fix plan by providing the issue number, which extracts root cause, affected files, scope, and testing requirements from an existing investigation report and saves the plan to wiki/issues/$ARGUMENTS/fix-plan.md.

A bug fix plan includes root cause analysis, affected files, in-scope changes, out-of-scope boundaries, testing requirements, validation steps, data remediation, and risk assessment extracted from the investigation report.

Yes, an investigation report from @investigate-bug must exist on the issue before generating a fix plan, as the tool extracts root cause and affected files from that report.

Out-of-scope boundaries are defined by extracting them from the investigation report, ensuring the fix plan clearly separates in-scope code changes from out-of-scope boundaries.

Yes, you can plan data remediation for a single issue as the fix plan includes data remediation steps alongside file changes and validation steps when needed.

The best way to document testing strategy is to extract testing requirements from the investigation report and include them in the fix plan as validation steps, ensuring the testing strategy aligns with the root cause and affected files.