agentic-controller

Reads PLAN.md and executes each migration step sequentially. Applies transformations file by file, consulting domain-specific reference patterns provided by loaded migration skills. Use after the plan stage has produced PLAN.md.

Migrates Java EE 7/8 applications (WebLogic, JBoss, WildFly) to Quarkus 3. Use when moving off a traditional Java EE application server to the Quarkus runtime, not just renaming javax to jakarta.

Reads a project and a goal statement, then produces PLAN.md in the repo root. The plan is specific to THIS project — real file paths, real dependencies, real layer ordering. Uses graphify to generate a code graph, then selectively reads complex files. Does NOT execute any changes. Output is always PLAN.md and nothing else. Use when starting a new migration to create the migration plan before any code changes.

Runs the project build command, parses compiler errors, applies conservative fixes, and iterates until the build passes or max iterations are reached. Use after the execute stage has finished migrating source files.

Migrates EJB components to CDI managed beans.

Migrates Maven POM files from Java EE to Jakarta EE.

Enforces that no javax.* imports remain after migration.

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.