code-modernizationlisted

# Code Modernization Use this skill for structured legacy modernization. Do discovery before rewrites, preserve behavior by default, and keep every recommendation tied to source evidence. ## When To Use Use this skill when the work involves: - Understanding a legacy system before changing it. - Mapping dependencies, call graphs, data lineage, or entry points. - Extracting calculations, validations, policies, or lifecycle rules from code. - Creating a modernization brief or migration sequence. - Transforming one legacy module into a target stack. - Reimagining a system from extracted intent rather than line-by-line porting. - Security hardening legacy code that will keep running during migration. Do not use it for ordinary small refactors in actively maintained code unless the user explicitly frames the task as modernization or behavior-preserving migration. ## Workspace Layout Default to this layout unless the user gives another one: ```text legacy/<system>/ # existing system; read-only by default analysis/<system>/ # discovery artifacts, diagrams, specs, findings modernized/<system>/ # transformed modules or new implementation ``` If the legacy code lives elsewhere, ask whether to adapt paths or have the user provide a symlink/copy. Never edit `legacy/` directly unless the user explicitly approves that exact change. Prefer writing remediation patches under `analysis/<system>/`. ## Core Workflow Follow this sequence: ```text assess -> map -> extract-ru