mm-riper

To enforce phase separation for complex software development tasks, you need a structured process that gates research, innovation, planning, execution, and review phases. This ensures disciplined progression by requiring user input before advancing to the next stage.

Managing multi-file refactoring with an unclear scope requires breaking down the chosen approach into ordered, reversible tasks during a dedicated planning phase. This follows initial research and innovation phases to fully understand the problem space first.

You need a structured software development process when a feature, refactor, or fix spans multiple files or has an unclear scope. It separates research, planning, and execution to prevent unmanaged deviations during complex task implementation.

To start a structured code review and task management workflow, invoke the process with your task in mind. You will then follow sequential phases, providing required user input at each phase gate to validate research, plans, and execution outcomes.

No, the execution phase requires following the plan meticulously without deviations. To maintain disciplined phase separation, the structured process validates the final work against the original plan during a dedicated review phase.

The innovation phase in complex task management works by generating multiple approaches to the problem after researching the current code. It ensures you evaluate various solutions before selecting one to break down into ordered tasks during planning.