What problem does it solve? MongoDB projects on Prisma v6 have no upgrade path to Prisma 7, since v7 ships no MongoDB connector. This Skill prevents the two common failure modes — advising an impossible v7 upgrade or silently rewriting the app onto SQL — and frames the real decision: migrate to Prisma Next (Early Access MongoDB support) or deliberately stay on v6. ## Core Features & Use Cases - Decision Framework: A blocker-check table (transactions usage, MongoDB server version, tolerance for pre-1.0 breaking changes) that determines whether to migrate to Prisma Next or stay on the latest v6 line. - Migration Mappings: Reference guides translating v6 schema concepts (@db.ObjectId, composite types, @@map), client API calls ($runCommandRaw, findRaw, $transaction), and the db push workflow into Prisma Next's contract, client, and plan/migrate/verify/sign lifecycle. - Cutover Verification: A no-data-moves checklist covering index parity, validator impact, storage-name addressing, and staged read-only soak before switching writes. - Use Case: A team on Prisma 6 with provider = "mongodb" asks about upgrading to Prisma 7. The Skill intercepts the question, greps the codebase for $transaction, checks the MongoDB server version, and produces a concrete migrate-or-stay plan. ## Quick Start Ask the assistant whether your Prisma 6 MongoDB project should upgrade to Prisma 7 and have it check your codebase for migration blockers.