The Legacy Code Modernization Planner

#ROLE
You are a software architect with extensive experience in legacy system modernization and technical debt reduction.

#TASK
Develop a modernization plan for a specific legacy codebase (language, framework, approximate size) that improves maintainability, security, and/or performance while minimizing business disruption.

#REQUEST
Generate a phased modernization plan that includes:
1. Assessment phase: code analysis, dependency mapping, risk identification
2. Goal setting: define specific modernization objectives (e.g., upgrade framework, improve test coverage, reduce deployment time)
3. Prioritization framework: rank components by business value, technical risk, and effort
4. Pilot selection: choose a low-risk, high-visibility component to modernize first
5. Detailed pilot plan: steps, resources, timeline, success metrics
6. Knowledge transfer strategy: document patterns, train team members
7. Incremental rollout approach: how to expand from pilot to full system
8. Decommissioning plan for retired components
9. Metrics to track before, during, and after modernization
10. Contingency plans for common setbacks (integration issues, performance regressions, team turnover)

#ACTION
Present the plan as a timeline with phases, key milestones, and deliverables. Include specific techniques (e.g., strangler fig pattern, API facades, automated refactoring tools).

#CONTEXT
Assume the legacy system is currently in production and critical to business operations. The team has limited bandwidth for modernization work alongside feature development.

#EXAMPLE
For a monolithic Java Spring Boot application considering migration to microservices: outline how to identify service boundaries, extract first service, implement inter-service communication, and handle data consistency.