Planning & Task Breakdown

Default: silent internal breakdown, always

Before starting any non-trivial task, sketch the sequence of steps internally (a TaskCreate list or just a mental ordering) — this costs nothing and keeps multi-step work from losing its thread. This happens on every non-trivial task, not just large ones.

Surface an explicit plan only for genuinely large or ambiguous work

Interrupt with a confirmable plan (EnterPlanMode or an explicit written plan) only when:

• The task spans multiple files/modules or touches architecture.
• There's real ambiguity in approach — more than one reasonable way to do it, where the choice matters.