Who should use the Multi-file Refactoring workflow?
Teams or solo builders working on development tasks who want a repeatable process instead of one-off tool experiments.
Execution Map
3-step pipeline — follow each step in order
1Setup · Step 1 of 3
Open task pageRefactor code
Prepare inputs and settings through Refactor code before running multi-file refactoring.
Why this matters
Refactor code sets up the foundation for multi-file refactoring; clean inputs here reduce downstream rework.
What you get
Inputs, context, and settings are ready so the workflow can move into execution without blockers.
2Input · Step 2 of 3
Open task pageCode Refactoring
Use Code Refactoring to build supporting assets that improve multi-file refactoring quality.
Why this matters
Code Refactoring strengthens multi-file refactoring by feeding better supporting material into the pipeline.
What you get
Supporting assets from code refactoring are prepared and connected to the main workflow.
3Core · Step 3 of 3
Open task pageMulti-file Refactoring
Execute multi-file refactoring with Multi-file Refactoring to produce the primary final deliverable.
Why this matters
This is the core step where multi-file refactoring actually happens, so it determines baseline quality for everything after it.
What you get
A first-pass final deliverable is generated and ready for refinement in the next steps.
More options