plan-data-migration
Skill0 starsChanged 16 days agoMITView on GitHub
Plan expand-then-contract data migration slices. Use when the user asks for a migration plan, expand/contract, dual-write plan, or /plan-data-migration. Do not expand and contract in the same change. Do not run the migration.
In this repository66 other files it gives its agents.
- AGENTS.mdAGENTS.md
- a11y-passSkill
- assess-changeSkill
- build-regression-packSkill
- charter-exploratorySkill
- classify-dataSkill
- commitSkill
- cut-releaseSkill
- data-changeSkill
- debugSkill
- design-experimentSkill
- diff-environmentsSkill
- draft-steercoSkill
- engineering-barSkill
- explain-codeSkill
- explore-codebaseSkill
- fix-ciSkill
- handoffSkill
- implement-changeSkill
- incident-triageSkill
- lean-reviewSkill
- map-dependenciesSkill
- map-design-handoffSkill
- map-processSkill
- open-prSkill
- performanceSkill
- plan-incrementSkill
- plan-rollbackSkill
- plan-uatSkill
- prioritize-backlogSkill
- production-passSkill
- ready-to-mergeSkill
- record-decisionSkill
- refactor-safelySkill
- revert-changeSkill
- review-architectureSkill
- review-changeSkill
- review-pipelineSkill
- security-passSkill
- shape-workSkill
- ship-notesSkill
- spec-analyticsSkill
- spec-observabilitySkill
- start-projectSkill
- synthesize-discoverySkill
- triage-blockersSkill
- triage-defectSkill
- update-raidSkill
- verify-uiSkill
- write-api-examplesSkill
- write-architectureSkill
- write-designSkill
- write-dev-tasksSkill
- write-docsSkill
- write-integration-contractSkill
- write-nfrSkill
- write-opportunitySkill
- write-prdSkill
- write-requirementsSkill
- write-runbookSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Do not implement. Do not put expand and contract in one slice.
- Distinctive: line 34
If you cannot name the current stored shape, stop.
- Distinctive: line 43
Read AGENTS.md if present.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Plan data migration
Order the safe slices. This is not data-change (that applies one slice) and not write-integration-contract.
Do not implement. Do not put expand and contract in one slice.
Is this the right skill?
| Signal | Do this instead |
| The contract/shape itself | write-integration-contract |
| Apply one expand or one contract | data-change |
| Examples only | write-api-examples |
Required inputs
- Current shape and desired shape (design, contract, or schema path)
AGENTS.md
If you cannot name the current stored shape, stop.
Human decisions (do not invent)
- Downtime window (default: none — expand/contract online)
- Backfill ownership
Procedure
- Read
AGENTS.mdif present. Read the current schema/contract and the desired one. - Find the home:
docs/data/migration-<slug>.md. - Open references/migration-template.md. Copy every heading. Write
n/awhen unused. - Slices in order: expand (add) → dual-write/read if needed → backfill → switch readers → contract (remove). Each slice separately reviewable.
- Each slice names the later
data-change(or sibling skill) and a rollback sentence. - No secret values.
Output
- Path:
docs/data/migration-<slug>.md - Template:
references/migration-template.md
Quality bar
- Current and desired shapes are named
- Expand and contract are different slices
- Each slice has a rollback sentence
- Unused headings are
n/a
Done
- Path
- Slice count
- Next skill:
data-changeon slice 1
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.