What problem does it solve? MongoDB projects on Prisma v6 have no upgrade path to Prisma 7, which 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-based decision table covering transaction usage, MongoDB server version, and Early Access risk tolerance to choose between migrating to Prisma Next or staying on v6. - API and Schema Mapping: Maps v6 client calls, raw queries, transactions, and schema concepts (ObjectId, composite types, storage names) to their Prisma Next equivalents. - Verified Cutover Checklist: Supplies a ten-step no-data-moves verification checklist covering index parity, validators, 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, checks the codebase for $transaction usage, and walks them through a staged 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.