modernization-flow

Modernization Flow - Execute Phases Sequentially

Context

This modernization process is designed to systematically analyze, specify, and implement code modernization/migration projects. The process is divided into phases that MUST be executed one-by-one.

Critical Requirements

• ONE PHASE AT A TIME: Read one phase file, execute it completely, update state file, then move to next phase.
• DO NOT SKIP PHASES: Each phase builds on the previous one.
• STATE TRACKING: After each phase, update agents/modernization-flow-state.md with completion status, keep this document concise.
• USER CONFIRMATION: Wait for user confirmation before proceeding to next phase.
• Make sure to have todo tasks for each phase! Do not skip phases!
• REMEMBER Do not put decisions/recommendations/suggestions/implementation code for the next phases in the output documents! The decisions are made at phase 6 and review at phase 7 AFTER full analysis. Respect that.
• MUST Create and update files that ARE EXPLICITLY stated here, ASK for permission to create any other file!
• MUST use grep/search on large files to read "table of contents" and then use line ranges to read what is needed.
• MUST use only applicable phases according to the target of the modernization (acquire user approval first and store it in state), as those phases are for multi-project cross-tech modernization. Do not take shortcuts within the phase!
• Prioritize ACCURACY over SPEED!
• THIS is very large workflow: MUST use best matching available separate subagents for each phase, top level agent is orchestrator, orchestrator must be smart with reading/writing files (avoid, fallback to grep and reading line-ranges, as those are very large)
• Phase subagents must contain additionally: "MUST APPLY PHASE <phase.md> — FULLY EXECUTE ALL STEPS", goal, context, original user request, inputs, expected outputs, and summary in the format useful for orchestrator, subagents must be informed they are used as subagents.