code-modernization

Full discovery & portfolio analysis of a legacy system — inventory, complexity, debt, relative scale

Generate a phased Modernization Brief — the approved plan that transformation agents will execute against

Mine business logic from legacy code into testable, human-readable rule specifications

Security vulnerability scan with a reviewable remediation patch — OWASP, CWE, CVE, secrets, injection

Dependency & topology mapping — call graphs, data lineage, batch flows, rendered as navigable diagrams

Reviews proposed target architectures and transformed code against modern best practice. Adversarial — looks for over-engineering, missed requirements, and simpler alternatives.

Mines domain logic, calculations, validations, and policies from legacy code into testable Given/When/Then specifications. Use when you need to separate "what the business requires" from "how the old code happened to implement it."

Deep-reads legacy codebases (COBOL, Java, .NET, Node, anything) to build structural and behavioral understanding. Use for discovery, dependency mapping, dead-code detection, and "what does this system actually do" questions.

Scaffolds one service of a reimagined system from the approved architecture and spec — project skeleton, domain model, API stubs, executable acceptance tests. Write access is scoped to its own service directory under modernized/.

Adversarial security reviewer — OWASP Top 10, CWE, dependency CVEs, secrets, injection. Use for security debt scanning and pre-modernization hardening.