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.

Writes characterization, contract, and equivalence tests that pin down legacy behavior so transformation can be proven correct. Use before any rewrite.

Migrates ONE project/module of an in-flight same-stack version uplift by applying a proven pilot playbook — minimal diff, then runs that unit's real build to prove it. Refuses to migrate anything if no playbook exists yet. Write access is scoped to its own unit's directory inside the uplift working

Identifies the breaking changes between two versions of the SAME stack (e.g. .NET Framework 4.8 → .NET 8, Java 8 → 17/21, Spring Boot 2 → 3) that actually bite a given codebase, and drives the ecosystem's migration tooling. Use for same-stack uplifts, where code is preserved and tweaked — not rewrit

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

Environment readiness check — analysis tools, build toolchain, source completeness, telemetry access

Multi-agent greenfield rebuild — extract specs from legacy, design AI-native, scaffold & validate with HITL

Where am I in the modernization workflow — artifact inventory, staleness, secrets hygiene, next step

Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests

Same-stack version uplift (e.g. .NET Framework 4.8 → .NET 8) — preserve the code, fix the version deltas, prove equivalence by running one test suite on both runtimes