agentsclimarketplace

Legacy modernization orchestrator

Skill autohandai/community-skills/legacy-modernization-orchestrator

A collection of curated, useful, and safe skills for Autohand Code CLI Agent

Install
npx -y skills add autohandai/community-skills --skill legacy-modernization-orchestrator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Orchestrate multi-agent legacy modernization assessment, planning, and code-conversion workflows.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.2 KB, 387 tokens by cl100k_base, as published. Nobody here has run it

Legacy Modernization Orchestrator

Overview

Use this skill to coordinate a multi-step modernization effort across discovery, assessment, conversion, testing, and handoff. The upstream project, atesibrahim/legacy-modernization-orchestrator, provides a general legacy modernization orchestration reference for agent-assisted work.

Compatibility: COBOL, legacy modernization, Codex, Claude, and Copilot.

Repository table context: listed as a Both-tool modernization repository with 2 stars, 3 contributors, 0 .NET skills, and 10+ Java modernization agents in the provided inventory.

Workflow

  1. Define the modernization objective, target platform, scope boundaries, success criteria, and non-goals.
  2. Build the asset inventory and classify each component by business function, technical complexity, dependency risk, and testability.
  3. Assign workstreams for discovery, rule extraction, code conversion, data migration, interface mapping, test generation, and documentation.
  4. Run conversion in bounded slices with a traceability record from source artifact to target artifact.
  5. Gate each slice on evidence: reviewed generated code, parity tests, stakeholder signoff, and unresolved-risk tracking.
  6. Produce an executive status summary and an engineer-facing handoff after each milestone.

Guardrails

  • Do not let orchestration hide uncertainty. Each agent or workstream should report assumptions, evidence, and confidence separately.
  • Keep legacy behavior preservation as the default unless stakeholders explicitly approve behavior changes.
  • Require rollback or coexistence planning for phased migration.
  • Read the upstream README and agent instructions before reusing orchestration prompts, scripts, or templates.

Expected Output

Return a modernization plan with workstreams, dependency map, migration backlog, acceptance gates, risk register, and current status.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.