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: Evaluates blockers like $transaction usage, MongoDB server version, and tolerance for pre-1.0 breaking changes to recommend migrating to Prisma Next or staying on v6. - API and Schema Mapping: Maps v6 client calls, raw queries, composite types, and ObjectId schemas to Prisma Next contract and ORM equivalents. - Cutover Verification: Provides a checklist for migrating code against the same database with index parity checks, validator impact assessment, and staged read-only soak testing. - Use Case: A team running Prisma 6 with provider = "mongodb" asks about upgrading to Prisma 7; the Skill explains v7 is impossible, checks the codebase for transaction blockers, and walks through a verified Prisma Next cutover. ## 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.
