migration-assessment

Run the 10-step assessment workflow: gather project context, scan structure, analyze dependencies, identify breaking changes, evaluate tests and security, then compute a weighted readiness score. A score at or above the configured threshold passes the gate to planning.

It supports version upgrades like Java 11 to 21, cross-language ports like Python to Rust, framework swaps like JDBC to JPA, database migrations like PostgreSQL to MongoDB, notebook conversions from .ipynb to .py, and platform or protocol changes such as REST to gRPC.

The score weights five dimensions: dependency portability at 30%, breaking change density at 25%, code complexity at 20%, test coverage at 15%, and security baseline at 10%. Each dimension is scored 0-100 and summed into a final weighted result compared against the configured threshold.

Yes, it falls back to native file reading when MCP servers are absent. Dependency scanning, test coverage, and security checks all have manual fallback procedures that parse build manifests and inspect source files directly.

The 7Rs are Retire, Retain, Relocate, Rehost, Replatform, Repurchase, and Refactor. Each component in the codebase is assigned one strategy with a rationale and effort estimate based on its dependency labels, breaking changes, and coupling to the source platform.

The gate is blocked and no files are written. The assessment identifies which dimensions underperformed, suggests specific remediations per dimension, and states whether reducing scope would push the score above the threshold.