plan-refactor

To plan a complex code refactor without context loss, use a formal eight-phase workflow with human gates and verification checkpoints. This process generates a self-contained implementation plan that ensures traceable decisions and safe, auditable change execution.

A phased workflow for software refactoring is a structured process enforcing exploration, scope freezes, and post-implementation audits. Use it for changes touching multiple files or layers, such as feature additions or bug fixes, to minimize risk and regressions.

To execute a code change plan after a context reset, generate a self-contained implementation plan beforehand. This verified plan allows a fresh agent to execute the refactor safely, ensuring traceability and preventing context loss during the implementation phase.

Yes, this multi-layer refactor planning workflow requires three mandatory human gates to govern plan creation and execution. These manual approval steps enforce gate reviews, scope freezes, and post-implementation audits to minimize risk and regressions.

Yes, you can use this structured workflow for bug fixes and feature additions. The eight-phase planning process is type-agnostic, making it suitable for any code change that touches multiple files or layers and requires strict verification and scope control.

The limitation of an eight-phase workflow for code changes is the overhead from mandatory human gates, scope freezes, and post-implementation audits. This heavy, structured process may be excessive for simple, single-file modifications that do not require strict traceability.