skills.rest
jason-hchsieh
jason-hchsiehCOMMUNITY
Explore all skills by this author →
GitHub

Recovery and Escalation Protocols

Detect, recover from, and escalate workflow blockers via structured rollback protocols.

Updated Feb 3, 2026
Search Tags:#debugging#rollback#blockers#recovery#process#workflows#escalation
One-click install
npx skills add https://github.com/jason-hchsieh/mycelium --skill recovery-and-escalation-protocols
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Recovery and Escalation Protocols
Source: https://github.com/jason-hchsieh/mycelium/tree/main/skills/recovery
Command: npx skills add https://github.com/jason-hchsieh/mycelium --skill recovery-and-escalation-protocols

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams detect, recover from, and escalate blockers and errors across any workflow phase, preventing cascading failures and reducing downtime.

Core Features & Use Cases

  • Failure detection and triage: Triggers and guidelines to identify when escalation is warranted.
  • Structured recovery workflows: Phase-based plan (reproduce, isolate, investigate, hypothesize, fix) with defined actions and checkpoints.
  • Escalation and rollback protocols: Clear paths to raise architectural reviews and safely rollback changes.
  • Audit and learning: Documentation of recovery actions and lessons learned for continuous improvement.

Quick Start

Initiate recovery by following the documented phases to reproduce, isolate, investigate, hypothesize, and verify fixes.

Frequently Asked Questions about Recovery and Escalation Protocols

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a structured recovery workflow for repeated workflow failures?▼

Establish a structured recovery workflow by following phase-based steps to reproduce, isolate, investigate, hypothesize, and verify fixes. This process detects blockers and prevents cascading failures across development cycles and production environments.

When should I trigger an escalation for a debugging blocker?▼

Trigger an escalation for a debugging blocker after three consecutive failed attempts. Escalation paths raise architectural reviews to handle blocking decisions and resolve complex external dependencies.

What is the best way to implement a rollback procedure during a production failure?▼

Implement a rollback procedure by following defined recovery protocols that safely revert changes during production failures. This structured approach reduces downtime and handles multi-step debugging effectively.

Can I document recovery actions for audit and continuous improvement?▼

Yes, you can document recovery actions and lessons learned for audit purposes. Centralized documentation of recovery workflows ensures continuous improvement and tracks how blockers were resolved.

Does this escalation protocol work across testing and development environments?▼

Yes, the escalation protocol applies across development cycles, testing, and production environments. It handles multi-step debugging and external dependencies to prevent cascading failures in any workflow phase.

Related Skills

Explore More Software Engineering Skills→
hbvg234hbvg234
1

agent-introspection-debugging

Capture failure state, diagnose root causes, and generate introspection reports for AI agent runs.

Community
Advanced
mostafasudomostafasudo
3

learn

Manage and retrieve project learnings with review, search, pruning, and export.

Community
Intermediate
tonyandrewmeyertonyandrewmeyer
1

iterate-fix

Triage build, deploy, and test failures with bounded retries and escalation.

Community
Advanced
yaresimeonthomasyaresimeonthomas

resolving-rollback-conflicts

Resolve git revert merge conflicts in CI/CD rollback workflows.

Community
Advanced