Feather Fall
Turn a hard crash into a controlled descent.
What This Skill Does
Feather Fall is the spell for bad situations that are already in motion. A deploy is going sideways, a service is thrashing, a queue is backing up, or an integration is failing faster than the humans can think. Instead of pretending you can teleport back to normal instantly, you slow the fall: circuit breakers, degraded modes, load shedding, safe defaults, and graceful shutdown paths. The point is not elegance. The point is buying time without multiplying damage. A good Feather Fall plan makes failure survivable and visible enough to recover from.
In this grimoire, Feather Fall is treated as a metaphorical spell with a shipping-now delivery profile.
Canonical reference input: Feather Fall (spell).
When To Use
- A live service, deploy, or workflow is failing and needs a safer landing path immediately.
- The right answer is graceful degradation, fallback behavior, or controlled shutdown rather than business-as-usual.
- You need to define what stays up, what gets dropped, and how to keep users from falling with the system.
Prerequisites
- No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.
Procedure
- Restate the target, the success condition, and any no-touch boundaries before taking action.
- Identify the failure that is already underway, including the blast radius if nothing changes.
- Choose the descent mechanisms that reduce harm fastest: feature flags, circuit breakers, throttles, queue draining, or static fallbacks.
- Define the minimal safe experience during the fall, along with the signals that prove the descent is stabilizing.
- Return the emergency sequence, operator checks, and the criteria for either recovery or a full shutdown.
- Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.
Deliverables
- A graceful-degradation or safe-landing sequence.
- Trigger thresholds and operator signals for entering and exiting fallback mode.
- A note on what user experience, data guarantees, or capacity are intentionally reduced during the descent.
Pitfalls / Guardrails
- Keep the metaphor anchored to a real mechanism instead of drifting into lore.
- Do not use graceful degradation to hide the incident from operators who need to respond.
- Fallback modes must protect data integrity and user safety before they protect polish or convenience.
Verification
- Check that the result includes every deliverable promised above.
- Check that confirmed facts, assumptions, and inferences are visibly separated.
- Check that the metaphor still maps cleanly to a real operational mechanism.
Example Invocation
/feather-fall design the fastest safe descent for this failing deploy, service, or workflow, including what should degrade first
1---2name: feather-fall-23description: Feather Fall is the spell for bad situations that are already in motion. A deploy is going sideways, a service is thrashing, a queue is backing up, or an integration is failing faster than the humans can think. Instead of pretending you can teleport back to normal instantly, you slow the fall: circuit breakers, degraded modes, load shedding, safe defaults, and graceful shutdown paths. The point is not elegance. The point is buying time without multiplying damage. A good Feather Fall plan makes failure survivable and visible enough to recover from.4license: CC0-1.05---6# Feather Fall7Turn a hard crash into a controlled descent.8## What This Skill Does9Feather Fall is the spell for bad situations that are already in motion. A deploy is going sideways, a service is thrashing, a queue is backing up, or an integration is failing faster than the humans can think. Instead of pretending you can teleport back to normal instantly, you slow the fall: circuit breakers, degraded modes, load shedding, safe defaults, and graceful shutdown paths. The point is not elegance. The point is buying time without multiplying damage. A good Feather Fall plan makes failure survivable and visible enough to recover from.10In this grimoire, Feather Fall is treated as a metaphorical spell with a shipping-now delivery profile.11Canonical reference input: Feather Fall (spell).12## When To Use1314- A live service, deploy, or workflow is failing and needs a safer landing path immediately.15- The right answer is graceful degradation, fallback behavior, or controlled shutdown rather than business-as-usual.16- You need to define what stays up, what gets dropped, and how to keep users from falling with the system.1718## Prerequisites1920- No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.2122## Procedure23241. Restate the target, the success condition, and any no-touch boundaries before taking action.252. Identify the failure that is already underway, including the blast radius if nothing changes.263. Choose the descent mechanisms that reduce harm fastest: feature flags, circuit breakers, throttles, queue draining, or static fallbacks.274. Define the minimal safe experience during the fall, along with the signals that prove the descent is stabilizing.285. Return the emergency sequence, operator checks, and the criteria for either recovery or a full shutdown.296. Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.3031## Deliverables3233- A graceful-degradation or safe-landing sequence.34- Trigger thresholds and operator signals for entering and exiting fallback mode.35- A note on what user experience, data guarantees, or capacity are intentionally reduced during the descent.3637## Pitfalls / Guardrails3839- Keep the metaphor anchored to a real mechanism instead of drifting into lore.40- Do not use graceful degradation to hide the incident from operators who need to respond.41- Fallback modes must protect data integrity and user safety before they protect polish or convenience.4243## Verification4445- Check that the result includes every deliverable promised above.46- Check that confirmed facts, assumptions, and inferences are visibly separated.47- Check that the metaphor still maps cleanly to a real operational mechanism.4849## Example Invocation50```text51/feather-fall design the fastest safe descent for this failing deploy, service, or workflow, including what should degrade first52```
Hmbown