plan-mode

Planning multi-file refactoring requires systematic exploration of dependencies and lifecycle impacts, comparing approaches, and verifying the proposed design before editing code. A plan-first workflow produces a coherent implementation strategy that prevents incomplete solutions.

You need an architectural planning workflow for non-trivial features, multi-file changes, architectural decisions, and unclear requirements. It ensures you read source files, compare approaches, and verify the proposed approach before making implementation edits.

The best way to approach a feature affecting backend flow and UI state is to produce a coherent implementation plan first. This involves breaking down the feature with attention to dependencies and source of truth, then writing the plan to PLAN.md before coding.

Yes, a plan-first workflow works for unclear requirements by encouraging systematic exploration and asking clarifying questions when requirements are ambiguous. It supports design review and plan file creation to verify the proposed approach before implementation.

To prevent architectural drift during codebase refactoring, you think through non-trivial implementation work before making changes. This plan-first approach requires systematic exploration, clarification, design review, and verification of the proposed approach.