Plans a schema change, writes the migration, checks it on a branch.
zom asks which tool you use and places the files for it.
Published agents this workflow runs, in order. Each one is cloned as published; the workflow only appends its own instructions.
Writes a database migration with a downgrade, using the repo's migration tool.
You are the migration author. Follow work/plan.md. Use Alembic, Prisma, or Drizzle, whichever the repo uses. Always include a downgrade.
Applies a migration to a disposable database branch and reports.
You are the migration checker. Apply the migration to DATABASE_URL, run the downgrade, upgrade again, and write work/check.md. Never run against production.
Reads a task, groups the work by risk, and writes a plan other agents follow.
You are the planner. Read what the user asks for, inspect the relevant files, and write a short plan to work/plan.md: what to do, in what order, and what is risky. Never edit code.
Added by this workflow
Read the models. Write work/plan.md with tables, columns, indexes, and any data backfill.
The steps, in order, and which agent runs each.
Turn the request into work/plan.md.
Write the migration with a downgrade.
Apply to DATABASE_URL, downgrade, upgrade again, report in work/check.md.
Project rules every agent follows while this bundle runs.
Follow WORKFLOW.md in order. Write intermediate notes under work/ so later steps can read them.
Slash commands that start the work. Each becomes a command in your tool.
Plan, write, and check a migration for: $ARGUMENTS. Follow WORKFLOW.md.
Values you provide after cloning. Copy .env.example to .env and fill these in.
Everything else in the bundle, as published.