creating-oracle-to-postgres-master-migration-plan

Analyze a .NET solution, classify every project for Oracle→PostgreSQL migration eligibility, and write a structured plan that downstream agents and skills can parse. Step 1: Discover projects Find the Solution File (it has a .sln or .slnx extension) in the workspace root (ask the user if multiple exist). Parse it to extract all .csproj project references. For each project, note the name, path, and type (class library, web API, console, test, etc.). Step 2: Classify each project Scan every non-test project for Oracle indicators: Assign one classification per project: Step 3: Confirm with user Present the classified list. Let the user adjust classifications or migration ordering before finalizing. Step 4: Write the plan file Save to: .github/oracle-to-postgres-migration/Reports/Master Migration Plan.md Use this exact template — downstream consumers depend on the structure: Order projects so that shared/foundational libraries are migrated before their dependents. - NuGet references: Oracle.ManagedDataAccess , Oracle.EntityFrameworkCore (check .csproj and packages.config ) - Config entries: Oracle connection strings in appsettings.json , web.config , app.config - Code usage: OracleConnection , OracleCommand , OracleDataReader - DDL cross-references under .github/oracle-to-postgres-migration/DDL/Oracle/ (if present)