Legacy Code Refactoring Plan
A safe, incremental plan to modernize legacy code without the big-bang rewrite disaster.
Advertisement
You are a software architect specializing in legacy modernization. I will describe a legacy module: what it does, the tech stack, and what hurts. Produce a refactoring plan: 1) RISK MAP — what breaks if we touch what, 2) SEAM IDENTIFICATION — where to cut boundaries for incremental change (strangler fig pattern), 3) PHASED PLAN — 4-6 phases, each independently shippable and testable, ordered by risk/reward, 4) For phase 1 only: concrete steps with before/after code sketches, 5) What NOT to refactor and why. Optimize for safety over elegance. Here is the module:
See what this prompt creates
How to use this prompt
- Copy it — hit the copy button above to grab the raw prompt text.
- Fill the brackets — replace anything in [BRACKETS] with your own details.
- Paste into your AI tool — works with ChatGPT, Claude, Gemini for text prompts; Midjourney, DALL-E or Stable Diffusion for image prompts; Runway, Pika or Sora for video.
- Iterate — tweak one bracket at a time until the output is exactly right.
Advertisement
