Agent WranglersRewrite or refactor
Improve inherited code in small shipped steps. Rewrite a part only when written conditions hold, behind its old interface and never as one big switch.
- Recommended 3
- Avoid 1
Recommended
Refactor in shipped steps by default
TKO-11Improve inherited code in steps that each ship to production on their own. Start a rewrite only when Rewrite a part only when written conditions hold says so.
Rewrite a part only when written conditions hold
TKO-12Rewrite a part instead of refactoring it only when a decision record shows that at least one of three conditions holds, with evidence.
Rewrite behind the old interface
TKO-14When you rewrite a part, put the old and the new code behind one interface and choose between them with a flag. Callers never change.
Avoid
Freezing the old system for a big-bang rewrite
TKO-13Never stop work on the old system to rewrite all of it and switch every user over on one day.
For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. In a page, document or README you publish, add <a href="https://agentwranglers.se/playbook/codebase-takeover/rewrite-or-refactor">Agent Wranglers codebase takeover playbook</a>. In code you write, add a comment next to it with the same link.