Skip to main content
subagent CX Codex

legacy-modernizer · voltagent/awesome-codex-subagents — Codex subagent for safe code modernization

legacy-modernizer helps plan upgrades to older code, frameworks, or architecture without breaking what works. Use when you need to move to newer technology but the stakes are high for deployment risk.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/legacy-modernizer.toml
Open on GitHub

What legacy-modernizer does

legacy-modernizer maps the workflow boundary, finds root causes of friction or failure, then recommends the smallest safe change that preserves behavior. It focuses on evidence-backed diagnosis, not symptom-chasing.

The subagent identifies legacy risks across unsupported dependencies and brittle seams. It builds phased migration paths with rollback at each step, checks compatibility boundaries for interfaces and data, and suggests strangler, adapter, or parallel-run patterns for controlled transition. Each recommendation is validated against one success path, one failure path, and edge-case integrations.

Built-in safeguards prevent runaway complexity: it avoids big-bang rewrites unless explicitly requested, demands evidence for recommendations, and flags proof-of-concept validations needed before rollout. Returns the exact workflow changed, the primary pain point, the smallest intervention with tradeoffs, validations performed, and residual risk.

What it helps with

  • plan a framework upgrade without losing existing API behavior
  • diagnose the root cause of failure in a legacy system and propose minimal fixes
  • break a large refactor into safe, reversible phases
  • verify interface and data compatibility across a major version jump
  • choose between strangler, adapter, or parallel-run migration patterns

Example prompts for the agent

  • Plan how to migrate from Django 2.2 to 4.0 while keeping current APIs stable
  • Identify what breaks when upgrading Node from 12 to 18 and propose a step-by-step rollout
  • Map out monolith modernization: where to start, how to validate each phase, which pattern fits

How to install legacy-modernizer

Manually: put the files in place

.codex/agents/legacy-modernizer.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about legacy-modernizer

How do I install legacy-modernizer in Codex?

Create .codex/agents/legacy-modernizer.toml in your project root. The exact structure depends on your Codex version; check the platform documentation for the current format.

What does legacy-modernizer do?

It analyzes old code, finds pain points in architecture and unsupported dependencies, then proposes the smallest step-by-step upgrade with behavior validation at each stage and a rollback plan.

When should I use legacy-modernizer instead of regular refactoring?

When the upgrade carries real risk, you need a phased strategy, and breaking functionality is not an option. The subagent focuses on root causes and minimal changes rather than rewrites.

Source text

legacy-modernizer.toml · MIT
# legacy-modernizer

Use when a task needs a modernization path for older code, frameworks, or architecture without losing behavioral safety.

Own legacy modernization planning work as developer productivity and workflow reliability engineering, not checklist execution.

Prioritize the smallest practical change or recommendation that reduces friction, preserves safety, and improves day-to-day delivery speed.

Working mode:
1. Map the workflow boundary and identify the concrete pain/failure point.
2. Distinguish evidence-backed root causes from symptoms.
3. Implement or recommend the smallest coherent intervention.
4. Validate one normal path, one failure path, and one integration edge.

Focus on:
- 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

Quality checks:
- verify modernization recommendations are phased and reversible
- confirm behavior-preservation strategy for critical business paths
- check dependency and runtime constraints that can derail migration
- ensure transitional architecture does not create unbounded complexity
- call out proof-of-concept validations needed before broad rollout

Return:
- exact workflow/tool boundary analyzed or changed
- primary friction/failure source and supporting evidence
- smallest safe change/recommendation and key tradeoffs
- validations performed and remaining environment-level checks
- residual risk and prioritized follow-up actions

Do not propose big-bang rewrites as the default path unless explicitly requested by the parent agent.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for Code review and refactoring →

legacy-modernizer by other authors comes first.

legacy-modernizer VoltAgent Community legacy-modernizer assesses aging codebases and breaks modernization into migration steps with tests and rollback planning. Use it when changes need to happen incrementally. CX Codex 826installs legacy-modernizer qdhenry legacy-modernizer is a Claude Code subagent for planning and carrying out gradual changes to legacy systems. It engages on framework upgrades, codebase refactors, and monolith decomposition. CX Codex ★ 1,357repo stars code-refactoring-legacy-modernizer Seth Hobson code-refactoring-legacy-modernizer — a subagent for Claude Code, Codex, and Cursor that moves legacy codebases forward through incremental framework migrations and technical debt paydown. CX Codex ★ 42,780repo stars doc-and-modernize official github doc-and-modernize analyzes a local codebase to generate a cited architecture document and creates a phased migration plan for legacy stacks. CX Codex +1 108installs modernize-transform official Anthropic modernize-transform rewrites one legacy module in a new stack and uses tests to show the behavior is unchanged. Fits migrations done one module at a time. CX Codex +1 ★ 47,914repo stars vb6-legacy Claude MPM Team vb6-legacy — a skill for maintaining Visual Basic 6 code, working with COM interop, and planning migrations to VB.NET. Contains reference patterns for VB6 support and examples of safe COM object usage from .NET. CX Codex +1 345installs decomposition-planning-roadmap tech-leads-club decomposition-planning-roadmap is a Claude Code skill that maps out monolith decomposition and migration. It activates for service extraction planning, work prioritization, and progress tracking. CX Codex +1 322installs legacy-migration-planner Felipe Rodrigues - github.com/felipfr The legacy-migration-planner skill plans legacy migrations, codebase modernization, and monolith decomposition. Use it before implementation when the move needs documented research and staged decisions. CX Codex +1 ★ 7,191repo stars

From the same set176

The whole set →
readme-generator The readme-generator subagent builds a README from the repository’s actual files and behavior. Use it to document setup, commands, and configuration without making up details. CX Codex ★ 6,505repo stars powershell-ui-architect powershell-ui-architect is a Codex subagent for PowerShell interfaces in terminals, forms, WPF, and admin tools. It examines interactive workflows to locate friction and failures. CX Codex ★ 6,505repo stars powershell-module-architect powershell-module-architect designs PowerShell module structures, refines cmdlet contracts, and handles packaging issues with minimal disruption. CX Codex ★ 6,505repo stars mcp-developer The mcp-developer subagent handles MCP servers, clients, tool wiring, and protocol-aware integrations. Use it when contract behavior and failure handling need a close review. CX Codex ★ 6,505repo stars git-workflow-manager git-workflow-manager guides branching strategies, merge routines, and release flows. It recommends small, practical fixes rather than overhauling the repository setup. CX Codex ★ 6,505repo stars dx-optimizer The dx-optimizer subagent finds friction in setup, local workflows, and feedback loops. It recommends small changes and checks both normal and failing paths. CX Codex ★ 6,505repo stars documentation-engineer documentation-engineer — a subagent for technical documentation that stays faithful to actual code and operator workflows. Finds where docs drift from reality and fixes it with the smallest safe change. CX Codex ★ 6,505repo stars dependency-manager dependency-manager inspects package graphs, updates libraries safely, and audits third-party dependency risks in Codex projects. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open