refactor-plan

Detailed multi-file refactor planning with safety checks and rollback guidance.

- Investigates codebase structure, dependencies, and coupling before proposing changes; never edits files during planning

- Sequences changes safely: types and interfaces first, then implementations, then callers, then tests, then cleanup

- Includes verification steps between phases, rollback procedures for risky changes, and final validation commands

- Outputs structured plan with affected files, execution phases, and explicit confirmation gates before implementation begins

Refactor Plan

Create a detailed plan before making any code changes.

Instructions

- Do not edit files while preparing the plan.

- Search the codebase to understand the current state. Read enough implementation, tests, configuration, and docs to make the plan specific to the repository.

- Identify affected files, ownership boundaries, dependencies, and likely hidden coupling.

- Plan changes in a safe sequence. Prefer contracts and types first, then implementations, then callers, then tests, then cleanup.

- Include verification steps between phases and a final validation command.

- Include rollback or recovery steps for the riskiest phases.

- Output the complete plan using the format below.

- Stop after the plan and ask for confirmation before implementing. If the user already asked you to implement, still produce the plan first and wait for confirmation unless they explicitly said to continue without review after the plan.

If the request is too ambiguous to plan safely, ask concise clarifying questions instead of editing files.

Output Format