Hire an AI Oracle to PostgreSQL migration test planner

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• Migration inventory and plan
• Baseline test scope and tests
• Behavior risks and release gates

How it does the job well

• Read the existing code, its conventions and its tests before changing anything. Match the project's patterns.
• Make the smallest change that fully solves the request. Keep unrelated refactors out.
• Reproduce a bug before fixing it, and add a test that fails without the fix.
• Treat input from users, files and networks as untrusted. Validate it at the boundary.

Mistakes it avoids

• Claiming code works without running it or its tests.
• Inventing APIs, package versions or settings instead of checking the installed ones.
• Changing behaviour outside the request, such as reformatting whole files or renaming public interfaces.

What a good result looks like

An example, not your task: You are moving a .NET app from Oracle to PostgreSQL and want to know what to test before you change any code.

• Master migration plan. Solution summary, a project inventory marked migrate or skip, and the order to move projects.
• Integration testing plan. Data access methods to test, test cases for each, seed data needs and Oracle and PostgreSQL differences to check.
• Oracle baseline tests. Integration tests that record what the Oracle code does today, with seed data and checks on exact values.
• Migration risk review. A table of behavior differences with where they apply, the risk, the fix and whether a test covers it.
• Verdict and decisions needed. Each risk marked addressed or not, open design choices and whether tests passed or were not run.

How the work is checked

• The changed files build, and the relevant tests and linters pass. The commands and results are shown.
• Each change is explained in one line with its reason, and risky areas are named.
• Any check that could not run is reported as NOT_RUN with what it needs.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

A second opinion

Before it hands back, your AI reviews the draft the way John Carmack would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Oracle to Postgres program planner. Share your .NET solution. Get a project inventory, migration scope and a master plan to track the work. The plan goes to step 2.
• Oracle migration test planner. Share your data access code. Get test scope and parity checks for an Oracle to Postgres migration. It reads the master plan and hands the testing plan to step 3.
• Oracle behavior baseline test writer. Share your Oracle data access code. Get tests that record what the code does before you change databases. It reads the testing plan and hands the baseline tests to step 4.
• Oracle migration risk reviewer. Share your migrated code. Get Oracle and PostgreSQL behavior gaps checked before release. It checks the migrated code against the baseline tests.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id plan-oracle-to-postgres-with-proof only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/plan-oracle-to-postgres-with-proof/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• The source files, notes or product facts for this job
• Your goal, deadline and limits
• Relevant earlier work, if available

Tools and access

• Claude Code or Copilot in your editor: They can read your procedures, calling code and tests together.
• A PostgreSQL test database: You need one to run the migration scripts and integration tests.

Functions and deliverables

• Oracle to PostgreSQL migration test planner: Share your .NET data-access code and database context. Get migration scope, baseline test drafts and behavior checks before release.
  • Migration inventory and plan
  • Baseline test scope and tests
  • Behavior risks and release gates
• Oracle to Postgres migration planner: Plan your Oracle to Postgres migration. Share your .NET solution and get a project inventory, a migration order and a master plan file.
  • A table with the number of projects to migrate, already migrated, skipped and test projects
  • A numbered list of each project with its path, its class and notes
  • A migration order with the reason for each place, shared libraries first
  • A saved file named MasterMigrationPlan.md to track the work
  Source: GitHub Copilot community.
• Oracle to Postgres migration test planner: Get an Oracle to Postgres migration test plan for your .NET data access code. It ranks risky methods and lists test cases to check parity.
  • A list of repositories, DAOs and services that touch the database, with method signatures
  • Methods ranked by migration risk
  • Test cases for each artifact
  • The seed data each test needs
  • A list of Oracle to PostgreSQL differences to check
  • A check that every database touchpoint has at least one test case
  Source: GitHub Copilot community.
• Oracle behavior baseline test writer: Write Oracle to PostgreSQL migration tests that record how your .NET data access code behaves on Oracle, before you switch databases.
  • Small seed data records for each scenario, in your project's style
  • A LookupConstants class with stable IDs and codes
  • Test classes that cover each database method with specific, repeatable checks
  • A review that confirms every check holds against the seed data alone
  Source: GitHub Copilot community.
• Oracle migration risk reviewer: Check Oracle to PostgreSQL migration work against 14 known behavior gaps and get a risk table, test coverage check and pass or fail verdict.
  • A table with one row per risk that applies to your code
  • For each risk, the affected file and the fix to apply
  • A note on any risk that needs a design decision from you
  • A check of whether your tests cover each risk
  • A pass or fail checklist
  Source: GitHub Copilot community.
• AI project context organiser: Share your project and next task. Get a short rules file, a focused file list and a clear handoff for later sessions.
  • A ready rules file for your project
  • A list of which files to load for each task
  • Rules for when to reset or trim the session
  • A checklist for spotting drifting answers
  Source: Addy Osmani.
• John Carmack: Find a bug, slow step or excess scope through John Carmack’s recorded approach. Follow the actual run, measure first and expose hidden state.
  • Your problem worked on the way John Carmack would: their questions, their method, their push-back
  • The answer or the work, in John Carmack's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step

Tasks you can use it for

• You are moving a .NET app from Oracle to PostgreSQL and want to know what to test before you change any code.
• You need baseline tests that record how the Oracle code behaves today, so differences show up after the move.
• You want a review of behavior risks before release, not after.

Limits to check before starting

• You are ready to change the code: use the Oracle to Npgsql code migrator or the Oracle to PostgreSQL procedure migrator.
• You only want to review code you already moved: use the Oracle migration risk reviewer on its own.
• Your move is not from Oracle to PostgreSQL, or your data access is not .NET: use the System migration and retirement planner or the System migration and rollback planner.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Add the complete skill pack to your AI.
• Share your goal and the files listed above.
• Ask it to follow the steps and mark any missing facts.
• Review the result before approving external actions.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/plan-oracle-to-postgres-with-proof for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.