Plan-Driven Change

Plan-first development cycle for larger changes. Combines brainstorming-style intent review with a tracked plan document and explicit implementation traceability.

If the change creates or reshapes module boundaries, introduces a new nested layer, changes public entrypoints, touches multiple layers where responsibilities may blur, or is happening in a repo with weak or duplicated boundary docs, load module-boundary-governance before finalizing the plan.

When to Use

• New capabilities, features, or modules
• Changes touching 3+ files or involving architectural decisions
• Anything where scope is unclear or risks exist

Skip for: bug fixes, one-liners, dependency bumps, config tweaks, and small maintenance edits. Act directly for those.

Phase 0: Discover Project Conventions

Before starting, quickly orient to the project: