Write a Degradation Plan for a Dependency Failure
Added 2026-11-03
A dead dependency should not take the whole feature down; define the fallback order.
Our feature depends on an external service (context below). Write the degradation plan: 1) list what breaks when the dependency is unavailable; 2) define three levels by importance — full, partial, minimum viable; 3) say what users see and which data stops updating at each level; 4) give the conditions for automatic switch and recovery; 5) point out where dirty data most likely appears during degradation; 6) explain how to tell users without alarming them.
Site original
Chinese original
How to use
降级方案要写在事故发生前，不是事故中。
Try tweaking it
- Have it restate requirements and constraints before writing code.
- Ask for the smallest change plus a rollback path, not a full-file rewrite.
What you should get
- A minimal, runnable change with copy-ready code
- Impact list: which files and call sites must follow
Common mistakes
- Asking it to touch ten files at once, then losing track of what broke what.
- Pasting only the error, with no code or version, and getting an unfixable answer.
How to check the output
- The change runs, can be rolled back, and touches nothing unrelated.
- Edge cases (empty, oversized, concurrent) are covered or explained.
Where it works
- Good for: having it restate requirements and constraints, then propose the smallest runnable change.
- Watch out: include versions and a minimal reproduction with the error, or the fix may look plausible but not fit.