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-based decision table covering transaction usage, MongoDB server version, and tolerance for pre-1.0 breaking changes. - Migration Mappings: Maps v6 schema concepts, client API calls, and the db push workflow to Prisma Next contracts, ORM calls, and the plan/migrate/verify/sign lifecycle. - Cutover Verification: Supplies a no-data-moves checklist covering index parity, validator impact, storage-name addressing, and staged read-only soak testing. - 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.