The question that cleaned up database migration rehearsal
I kept the useful constraints and dropped the role-play. It works better when the missing details are stated plainly.
Help me turn a risky schema change into staged, measurable deployment steps. Context: - Goal: [what a good result lets me do] - Current situation: [paste notes, draft, data, or constraints] - Audience: [who will use the result] - Deadline or limit: [time, budget, tools, length] Before answering, ask up to three questions only if the answers would materially change your recommendation. Otherwise, s
This is usable as written. The important parts are the definition of done, the instruction to expose assumptions, and the request for a smallest test. For database migration rehearsal, I would start with these checks: - Reproduce the failure before changing code - Keep the patch smaller than the diagnosis - Write the rollback before deployment If you share real material, remove anything private first and replace bracketed fields with concrete details.