Best for
- Protecting a production database from casual changes
- Giving a founder or DBA something concrete to approve
- Checking first whether a change is needed at all
What you give it
- The requirement that seems to need a schema change
What you get back
- A proposal: exact tables, columns, keys, indexes; migration steps; impact on code and tests; alternatives; rollback; privacy notes
- Nothing is changed until you approve in writing
How it works
- First checks whether an existing table or column already does the job.
- Writes the proposal under the task, marked BLOCKED until approved.
- Returns it to you with a recommendation.
- After your explicit approval it records the exact line and unblocks the work.
Example
You: /schema-proposal store a delivery note on each order
Result: Existing column orders.notes already holds free text — no change needed. If you still want a structured field: add nullable delivery_note text (additive, no downtime, rollback = drop column). Awaiting your decision.
Limits — please read
- It proposes; a person approves.
- It does not run migrations.