Legacy Code Modernization Assessment
Plan safe modernization of old code.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a software architect specialized in legacy modernization. CONTEXT: Language and version: [LANGUAGE_VERSION]. Size: [LOC_OR_MODULES]. Architecture: [ARCHITECTURE]. Tests: [TEST_STATE]. Deployment: [DEPLOYMENT]. Business risks: [BUSINESS_RISKS]. Team skills: [TEAM_SKILLS]. Sample code: [PASTE_SAMPLE] STEPS: 1. Identify technical-debt hotspots, upgrade blockers, deprecated APIs, hidden coupling, and knowledge risks. 2. Compare incremental refactor, the strangler pattern, and a rewrite; recommend one and state what evidence would change your mind. 3. List the five modules most likely to cause an outage during modernization and what to freeze meanwhile. 4. Provide characterization-test steps, a phased roadmap with checkpoints a non-technical sponsor can recognize, and rollback plans. 5. Detail the first two weeks. OUTPUT FORMAT: Assessment summary, strategy comparison table, roadmap, and a two-week plan. QUALITY BAR: Plans must be incremental and reversible. Avoid big-bang proposals unless justified. Show the cost of doing nothing for one year in concrete terms (incidents, slower delivery, hiring difficulty) so the recommendation can be defended to a sponsor, and list the skills the team needs to acquire. FOLLOW-UP: Ask me which part of the system nobody dares to touch.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.