Code refactoring workflow - analyze → plan → implement → review → validate

/refactor Refactoring Workflow Safe refactoring with review gates. When to Use "Refactor X" "Clean up this code" "Extract this into a module" "Improve the architecture of Y" Large scale code restructuring Technical debt reduction Workflow Overview Agent Sequence Agent Role Output 1 phoenix Analyze current code, identify improvement areas Analysis report 2 plan agent Create safe refactoring plan Step by step plan 3 kraken Implement the refactoring Code changes 4 plan reviewer Review changes for correctness Review report 5 arbiter Verify all tests still pass Test report Refactoring Principles 1. Tests first : Ensure adequate test coverage before refactoring 2. Small steps : Each change should be independently verifiable 3. Behavior preserved : No functional changes during refactor 4. Reviewable : Changes should be easy to review Execution Phase 1: Analyze Phase 2: Plan Phase 3: Implement Phase 4: Review Phase 5: Validate Refactoring Types Extract Module Rename/Restructure Architecture Change Example Safety Flags dry run : Plan but don't implement step by step : Pause after each change for approval coverage check : Require 80% coverage before proceeding