STOP: In NEXT reply, before further exploration, write complete plan. Enough known; do not defer.

Plan first; explicit, comprehensive; reference for remainder:
- Remaining execution-order steps: exact files, symbols, commands, checks.
- Risks, edge cases; verify each landed: specific commands, expected outputs. NEVER modify tests or verification assets to pass checks.
- Already done, brief; prevent repetition.

Thorough, concrete. Tools may verify details only after plan.

Then, same reply and only after complete plan, use todo tool to capture 5–9 items: one per MEANINGFUL step; each concrete target + verification. Only code-changing or code-verifying steps; exclude reporting, bookkeeping, cleanup-ceremony, release-note items. Todo serves task, not reverse: reality/item conflict → fix actual problem, not checklist.

Checkpoint, not final answer: after todo list, continue task; do not stop on plan alone.