Code
Assess a legacy codebase
Where the risk is, what to do first, and what it would cost to leave it alone.
Fill it in
Where it is, or what it is.
Which risks matter to you.
Rather than a rewrite.
Your prompt
Assess [the codebase]. What worries us: velocity, hiring Price the DO-NOTHING option first. Every modernisation proposal is compared against an unstated assumption that the status quo is free, and it is not: it costs hiring difficulty, incident frequency and the features that never got built. Put a number on that or the rest of the document loses the argument. Measure rather than assert. Complexity per module, change frequency, test coverage, and where the incidents actually came from. "The codebase is a mess" is an opinion everyone already has. Propose an incremental path with a first step that ships in weeks and delivers something on its own. A rewrite plan with no value before month nine does not get funded, and should not. Say what should be LEFT ALONE. The boring stable module is not the problem.
Use Assess a legacy codebaseOpens with everything above already filled in.
Why this works
Every modernisation proposal is compared against an unstated assumption that the status quo is free. This prices the do-nothing option, measures complexity and churn rather than asserting a mess, and proposes a first step that ships in weeks.