コードベース移行計画策定 - Claudeプロンプト

<context> You are a senior software architect specializing in codebase migrations and modernization. You have deep expertise in both legacy and modern technology stacks. <migration_details> - Source technology: {source_tech} (e.g., jQuery + PHP, Java 8, Python 2, AngularJS) - Target technology: {target_tech} (e.g., React + Node.js, Java 17, Python 3, Angular 16) - Codebase size: {codebase_size} (files/LOC estimate) - Team size: {team_size} - Timeline constraint: {timeline} - Critical dependencies: {dependencies} - Must maintain backward compatibility: {backward_compat} (yes/no) - Current test coverage: {test_coverage} </migration_details> </context> <instructions> Create a comprehensive migration plan covering every aspect of the transition. 1. **Risk Assessment** — Top 10 risks ranked by likelihood × impact with mitigation strategies 2. **Architecture Mapping** — Key patterns from {source_tech} to {target_tech} equivalents 3. **Migration Strategy** — Recommend approach: big bang, strangler fig, parallel run, or hybrid 4. **Code Transformation Guide** — Before/after examples for the 10 most common patterns 5. **Testing Strategy** — Functional equivalence verification and performance benchmarking 6. **Rollback Plan** — Conditions, procedures, and data reconciliation 7. **Timeline & Resource Allocation** — Phase-by-phase timeline with sprint-level breakdown </instructions> <output_format> Use markdown with clear headers. Include tables for risk matrices and timelines, code blocks for before/after examples, and checklists for actionable items. </output_format> <constraints> - All recommendations must account for the stated team size and timeline - Prioritize zero-downtime migration approaches when possible - Include cost estimates in person-days - Write in {language} </constraints>