plan-mode

To plan complex system changes, generate a structured PLAN.md that documents exploration, clarifications, design decisions, and a concrete implementation plan. This reduces architectural drift by mapping scope, dependencies, and risks before touching code.

You need a plan document for multi-file refactoring when scope or dependencies are unclear, or when making architectural decisions. It captures design decisions, acceptance criteria, and milestones to ensure alignment and safer rollouts.

The best way to document architectural decisions is by creating a PLAN.md file. It explicitly captures your design decisions, acceptance criteria, and lifecycle considerations, ensuring long-term maintainability and alignment during system design.

Planning before coding improves system reliability by enforcing structured exploration and review steps. This process maps risks and dependencies early, reducing architectural drift and ensuring stepwise execution guidance for safer rollouts.

Yes, you can use this planning workflow for uncertain project requirements. It includes explicit steps for exploration and clarification to map scope and dependencies before finalizing the design and implementation plan.

Starting architectural changes without a plan risks architectural drift and reduced reliability. Without a PLAN.md documenting milestones and acceptance criteria, you lack the stepwise execution guidance needed for safe rollouts and maintainability.