What problem does it solve? MongoDB projects on Prisma v6 have no upgrade path to Prisma 7 because v7 ships no MongoDB connector, leaving teams without clear guidance on whether to migrate to Prisma Next or stay on v6. ## Core Features & Use Cases - Decision Framework: Provides a blocker-check decision table for choosing between migrating to Prisma Next (Early Access MongoDB support) or deliberately staying on the latest v6 line. - API and Schema Mapping: Maps v6 client calls, raw queries, transactions, and schema concepts (ObjectId, composite types, storage names) to their Prisma Next equivalents. - Cutover Verification: Supplies a no-data-moves checklist covering index parity, validator impact, transaction inventory, and staged read-only soak before cutover. - Use Case: A team on Prisma 6 with MongoDB asks about upgrading to Prisma 7; the Skill explains v7 is impossible for MongoDB, greps the codebase for $transaction usage, checks the MongoDB server version, and plans the Prisma Next migration. ## Quick Start Ask the assistant to evaluate whether your Prisma v6 MongoDB project should migrate to Prisma Next and to check the codebase for migration blockers.
