Covers safe additive changes (optional fields, new tables, indexes) that require no migration code, and breaking changes (required fields, type changes, renames) that need custom migration functions
Provides patterns for batch processing, scheduled migrations via cron jobs, and dual-write strategies to maintain app availability during transitions
Fetches migration-helper from get-convex/agent-skills and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/migration-helper
Restart Cursor to activate migration-helper. Access via /migration-helper in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Safely migrate Convex schemas and data when making breaking changes.
When to Use
Adding new required fields to existing tables
Changing field types or structure
Splitting or merging tables
Renaming fields
Migrating from nested to relational data
Migration Principles
No Automatic Migrations: Convex doesn't automatically migrate data
Additive Changes are Safe: Adding optional fields or new tables is safe
Breaking Changes Need Code: Required fields, type changes need migration code
Zero-Downtime: Write migrations to keep app running during migration
Safe Changes (No Migration Needed)
Adding Optional Field
// Beforeusers:defineTable({ name: v.string(),})// After - Safe! New field is optionalusers:defineTable({ name: v.string(), bio: v.optional(v.string()),})
Adding New Table
// Safe to add completely new tablesposts:defineTable({ userId: v.id("users"), title: v.string(),}).index("by_user",["userId"])
Adding Index
// Safe to add indexes at any timeusers:defineTable({ name: v.string(), email: v.string(),}).index("by_email",["email"])// New index
Breaking Changes (Migration Required)
Adding Required Field
Problem: Existing documents won't have the new field.
Solution: Add as optional first, backfill data, then make required.
// Step 1: Add as optionalusers:defineTable({ name: v.string(), email: v.optional(v.string()),// Start optional})// Step 2: Create migrationimport{ internalMutation }from"./_generated/server";import{ v }from"convex/values";exportconst backfillEmails =internalMutation({ args:{},handler:async(ctx)=>{const users =await ctx.db.query("users").collect();for(const user of users){if(!user.email){await ctx.db.patch(user._id,{ email:`user-${user._id}@example.com`,// Default value});}}},});// Step 3: Run migration via dashboard or CLI// npx convex run migrations:backfillEmails// Step 4: Make field required (after all data migrated)users:defineTable({ name: v.string(), email: v.string(),// Now required})
Changing Field Type
Example: Change tags: v.array(v.string()) to separate table
// Step 1: Create new structure (additive)tags:defineTable({ name: v.string(),}).index("by_name",["name"]),postTags:defineTable({ postId: v.id("posts"), tagId: v.id("tags"),}).index("by_post",["postId"]).index("by_tag",["tagId"]),// Keep old field as optional during migrationposts:defineTable({ title: v.string(), tags: v.optional(v.array(v.string())),// Keep temporarily})// Step 2: Write migrationexportconst migrateTags =internalMutation({ args:{ batchSize: v.optional(v.number())},handler:async(ctx, args)=>{const batchSize = args.batchSize ??100;const posts =await ctx.db
.query("posts").filter(q => q.neq(q.field("tags"),undefined)).take(batchSize);for(const post of posts){if(!post.tags || post.tags.length ===0){await ctx.db.patch(post._id,{ tags:undefined});continue;}// Create tags and relationshipsfor(const tagName of post.tags){// Get or create taglet tag =await ctx.db
.query("tags").withIndex("by_name", q => q.eq("name", tagName)).
✓
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
›Access to product documentation and roadmap tools (Jira, Notion, etc.)
›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share effective prompts with product team
Common Pitfalls
⚠Not validating competitive research—verify facts before sharing
⚠Accepting user stories without involving engineering team
⚠Over-relying on frameworks without qualitative judgment
⚠Not customizing outputs to company culture and communication style
⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
+Validate research and competitive analysis with real data
+Collaborate with engineering when generating technical requirements
+Customize frameworks and templates to your company context
+Use skill for first drafts, refine with stakeholder input
+Document successful prompt patterns for PM tasks
+Combine AI efficiency with human judgment and intuition
✗ Don't
−Don't publish competitive analysis without fact-checking
−Don't finalize user stories without engineering review
−Don't make prioritization decisions solely on AI scoring
−Don't skip customer validation of generated requirements
−Don't ignore company-specific context and culture
💡 Pro Tips
★Provide context: company goals, constraints, customer feedback
★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
1Basic: user stories, feature specs, status updates
