Documentation
README
AWS Transform
CRITICAL: Route Before Anything Else
STOP. Before reading files, analyzing code, or starting any workflow, identify the workload first, then route.
Step A: Identify the workload
Look for an explicit workload signal in the user's request — a named technology (.NET, VMware, SQL Server/Aurora/Oracle/MySQL, mainframe/COBOL), workload-specific terminology (Hyper-V, EC2 rehost, stored procs, CICS, JCL), or file/project signals already in the conversation. If no signal is present, treat the request as workload-unspecified.
Step B: Apply workload-specific routing
Workload-specific rules ALWAYS win over the keyword list in Step C. Do not let "analysis" or "tech debt" phrasing override these.
This is the opening of the README. Read the full README on GitHub.