Plan an additive database migration
Plan {{CHANGE}} for {{PROJECT_NAME}}. Inspect schema and callers, prefer additive changes, and define backup, compatibility, restore, and rollout steps. Produce a plan before execution.
Define the problem
Plan {{CHANGE}} for {{PROJECT_NAME}}. Inspect schema and callers, prefer additive changes, and define backup, compatibility, restore, and rollout steps. Produce a plan before execution.
Inspect prerequisites
Read project instructions and relevant configuration. Record the current state, use sample data, and confirm a recovery point.
Make a bounded plan
Identify the smallest change, its affected files, and a testable expected result. Keep publication separate.
Implement in small steps
Use the linked prompt with real project details. Review each stage before extending it. Preserve unrelated work.
Verify and debug
Rehearse on disposable data, compare counts and constraints, and verify restoration.
Review and hand off
Inspect the diff and document changes, passed/failed/unrun checks, remaining limits, and recovery. Ask the owner to approve any live deployment.
Prompt library
GOAL:
Plan {{CHANGE}} for {{PROJECT_NAME}}. Inspect schema and callers, prefer additive changes, and define backup, compatibility, restore, and rollout steps. Produce a plan before execution.
CONTEXT / INPUT:
Project: {{PROJECT_NAME}}. Read relevant files and project instructions first. Ask only about material missing information.
SCOPE:
{{SCOPE}}
DO NOT:
Do not overwrite unrelated work, expose secrets, delete data, publish, or deploy. Respect {{CONSTRAINT}}.
EXPECTED OUTPUT:
A reviewable result with changed files or findings, and a concise explanation.
ACCEPTANCE CRITERIA:
{{SUCCESS_CRITERIA}}
VERIFY:
Rehearse on disposable data, compare counts and constraints, and verify restoration.
REPORT:
Report changes, reasons, passed/failed/unrun checks, remaining limitations, and recovery steps. Never claim a check passed without evidence.Common mistakes
Missing inputs, incorrect working folders, and unverified commands are common failure points. Stop at the failing step and gather evidence before trying again.