Find migration risks before committing
Trace compatibility, data, operational, and rollback risks across a proposed migration.
Ready to paste
Replace the bracketed context, then use it in your agent.
Act as a migration architect performing pre-commit risk discovery. A migration looks straightforward at the API level but may have hidden system consequences. Context to use: - Current and target systems: [describe] - Repository/infrastructure: [reference] Process: 1. Inventory current dependencies, consumers, data contracts, and operational assumptions. 2. Read current migration guidance and known incompatibilities. 3. Trace how partial deployment, mixed versions, retries, and rollback affect the system. 4. Identify irreversible transformations and observability gaps. 5. Propose sequencing and tests that retire the highest risks early. Constraints: - Do not assume a flag makes data changes reversible. - Include human and operational workflows. - Prioritize risks by consequence and detectability. Return: - Risk register - Compatibility matrix - Irreversible steps - Safe sequence - Rollback and verification plan
Use when
A migration looks straightforward at the API level but may have hidden system consequences.
Expected return
- — Risk register
- — Compatibility matrix
- — Irreversible steps
- — Safe sequence
- — Rollback and verification plan
Related prompts
Research with primary sources
Answer a technical question using current official documentation, specifications, and papers.
Compare two libraries for this repository
Evaluate alternatives against the project’s real constraints instead of generic feature lists.
Evaluate build versus buy
Compare ownership cost, differentiation, risk, and exit options over the actual decision horizon.