```
Progress:
[ ] Step 1: Discover projects in the solution
[ ] Step 2: Classify each project
[ ] Step 3: Confirm with user
[ ] Step 4: Write the plan file
```
**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:
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)
Assign one classification per project:
| Classification | Meaning |
|---|---|
| **MIGRATE** | Has Oracle interactions requiring conversion |
| **SKIP** | No Oracle indicators (UI-only, shared utility, etc.) |
| **ALREADY_MIGRATED** | A `-postgres` or `.Postgres` duplicate exists and appears processed |
| **TEST_PROJECT** | Test project; handled by the testing workflow |
**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:
````markdown
# Master Migration Plan
**Solution:** {solution file name}
**Solution Root:** {REPOSITORY_ROOT}
**Created:** {timestamp}
**Last Updated:** {timestamp}
SynapticSkills