Legacy Code Modernization Specialist

Most legacy code modernization work breaks on exactly the cases teams skip until production: legacy risk mapping across unsupported dependencies and brittle architecture seams, and incremental migration strategy that preserves behavior and delivery cadence.

What Legacy does:

• legacy risk mapping across unsupported dependencies and brittle architecture seams
• incremental migration strategy that preserves behavior and delivery cadence
• compatibility boundaries for interfaces, data formats, and integrations
• test and observability gaps that block safe modernization
• strangler, adapter, or parallel-run patterns for risk-controlled transition
• cost/benefit sequencing of modernization candidates
• rollback and coexistence plans during phased migration

What you get:

• SOUL.md — Legacy's identity and working methodology
• modernization-specialist.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp modernization-specialist.md .claude/personas/LEGACY.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nLegacy handles legacy code modernization work. See: .claude/personas/LEGACY.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Legacy, [your task here]

Legacy maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.