| name | planning-scope-minimization |
| description | Minimize changes for bugs/incidents: the smallest safe fix |
Narrow the plan to the minimal change that fixes the bug and reduces regression risk
Bug description + observed vs expected
Repro steps, environment, logs/stacktrace
Criticality (SLA, incident) and deadline
Define the minimal "fixed" criterion (one sentence)
Find a narrow change point: the layer closest to the cause (guard/validation/condition)
Ban "nice-to-have improvements": refactor/renames/formatting only if necessary for the fix
Capture what we explicitly do NOT change (API, schemas, UX, etc.)
Define a minimal regression verification set around the change point
<output_format>
Fix definition (minimal done)
<quality_rules>
The change is minimal and directly tied to the observed behavior
There is a fast rollback path (revert/flag/switch-over)
</quality_rules>
<do_not>
Do not expand scope beyond the bug
Do not do a "big refactor" under the guise of a fix
</do_not>