Modernizing existing projects
Codex plugin for governing large software projects from discovery through release and operations.
npx -y skills add VKK-00/agentic-project-lifecycle --skill modernizing-existing-projectsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 16 days oldThe repository was created 16 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 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
Use when changing a legacy or brownfield system with unclear behavior, weak tests, old dependencies, compatibility constraints, risky data migrations, public contracts, staged replacement, or decommissioning work.
The file declares its own license as Apache-2.0. 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
1.8 KB, as published. Nobody here has run it
Modernizing Existing Projects
Modernize from executable truth toward a safer target in reversible slices. Do not begin with a clean-room rewrite proposal.
Establish current truth
- RULE-MOD-01: Inventory runtime entry points, critical workflows, external contracts, data ownership, deployments, telemetry, incidents, and actual consumers before selecting a target architecture.
- RULE-MOD-02: Add characterization tests or production-derived contract checks around behavior that must survive. Distinguish intended behavior from accidental behavior explicitly.
Migrate reversibly
- RULE-MOD-03: Prefer strangler slices, adapters, and stable seams over a big-bang rewrite unless an explicit constraint makes incremental migration impossible.
- RULE-MOD-04: Use expand-and-contract changes for schemas and public interfaces. Define compatibility windows, dual-read/write rules where needed, cutover criteria, and rollback for every slice.
- RULE-MOD-05: Rehearse data migration and reconciliation on production-shaped data. Measure loss, duplication, ordering, latency, and recovery rather than trusting a successful command exit.
- RULE-MOD-06: Decommission only after traffic, data, consumers, alerts, support procedures, and rollback windows prove the old path is no longer required.
Read brownfield discovery, migration patterns, and cutover and decommission.