failure

Diagnose and triage session failures in autoboard orchestration workflows.

3|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/willietran/autoboard --skill failure-willietran
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: failure
Source: https://github.com/willietran/autoboard/tree/main/skills/failure
Command: npx skills add https://github.com/willietran/autoboard --skill failure-willietran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose session failures, arbitrate escalations, handle permission denials, cascade dependency blocks, and retry with adjusted briefs

Core Features & Use Cases

  • Failure context collection: Gather and synthesize the failure context from exit codes, logs, status files, and progress markers to inform remediation.
  • Failure classification: Distinguish between permission denials, escalation disputes, dependency cascades, and ordinary task failures.
  • Escalation arbitration: Provide a structured framework to arbitrate reviewer concerns and decide on retry or remediation actions.
  • Retry and recovery guidance: Propose adjusted briefs and preserve the worktree to re-run failed tasks with improved instructions.
  • Dependency-aware blocking: Block downstream sessions when upstream failures occur and unblock only after upstream success.

Quick Start

Explain the failure context to the system and let it guide you through diagnosis, escalation, and retry steps.

Frequently Asked Questions about failure

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

FAQPage Schema
How do I diagnose and triage failed workflow sessions automatically?

To diagnose failed workflow sessions, this Skill interprets exit codes, logs, and status files to classify failures like permission denials or dependency cascades, providing structured remediation and retry guidance.

What is the best way to handle escalation disputes in orchestration workflows?

Handling escalation disputes involves structured arbitration of reviewer concerns using failure context and manifests. The system decides whether to retry tasks with adjusted briefs or escalate, ensuring disputes are resolved systematically without blocking downstream sessions unnecessarily.

How do I block downstream sessions when an upstream dependency cascade fails?

Blocking downstream sessions during dependency cascades requires checking upstream status files and progress markers. This Skill automatically blocks dependent sessions after upstream failures and resumes them only when the upstream session achieves a successful state.

Can I retry a failed task with adjusted briefs while preserving the worktree?

Yes, you can retry failed tasks with adjusted briefs while preserving the worktree. The Skill proposes recovery guidance by interpreting failure context and modifying instructions, allowing you to re-run the task without losing previous progress or environment setup.

How does failure classification distinguish between permission denials and ordinary task failures?

Failure classification distinguishes permission denials from ordinary task failures by analyzing exit codes, logs, and design docs. It identifies specific denial patterns and escalation disputes, separating them from standard task errors to determine appropriate retry or block actions.

When should I block or resume sessions during autoboard orchestration failures?

You should block sessions when upstream dependency cascades or permission denials occur, and resume them only after upstream success or escalation arbitration. The Skill evaluates failure context and status files to determine whether blocking or resuming is the correct remediation action.