Legacy Code Assessment
# Legacy Code Assessment
## Situation
You've inherited an aging or unloved piece of code and must decide how to treat it: invest (improve in place), rewrite (replace it), or leave (don't touch it yet). You want the call made on evidence — cost of ownership, blast radius, changeability — not on how unpleasant the code is to read.
## The Promptwhen to use it
Community prompt sourced from the open-source GitHub repo shiphrahx/AI-for-engineering-leaders (MIT). A "Legacy Code Assessment" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
businesscommunitygeneral
source
shiphrahx/AI-for-engineering-leaders · MIT