fusion-rescue

Resolve stalled software development tasks through multi-agent deliberation and synthesis.

10|Updated May 9, 2026
One-click install
npx skills add https://github.com/jcwleo/oh-no-harness --skill fusion-rescue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fusion-rescue
Source: https://github.com/jcwleo/oh-no-harness/tree/main/plugins/oh-no-harness/skills-claude/fusion-rescue
Command: npx skills add https://github.com/jcwleo/oh-no-harness --skill fusion-rescue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill resolves complex software development tasks that have stalled due to inconclusive debugging, contradictory evidence, or blocked planning, preventing the need for manual intervention or project abandonment.

Core Features & Use Cases

  • Bounded Deliberation: Employs a three-panel ensemble (primary, adversarial, pragmatic) to synthesize diverse perspectives on a single problem.
  • Escalation Logic: Provides a structured path to unblock stalled debugging or architectural decisions without creating new, unapproved proof architectures.
  • Use Case: When a critical bug remains unresolved after multiple debugging attempts, use this Skill to generate a synthesized root-cause analysis and a verified path forward.

Quick Start

Invoke the fusion-rescue skill to perform a multi-agent analysis on the current stalled debugging task.

Frequently Asked Questions about fusion-rescue

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

FAQPage Schema
How do I resolve stalled debugging when multiple attempts fail to find the root cause?

Stalled debugging is resolved through a multi-agent deliberation process that synthesizes diverse perspectives to identify contradictions and generate a verified root-cause analysis for actionable next steps.

What is multi-agent synthesis for architectural deadlocks?

Multi-agent synthesis for architectural deadlocks is a bounded deliberation method using a three-panel ensemble to evaluate contradictory evidence and recommend a structured path forward without unapproved architectures.

When should I escalate a blocked software workflow instead of continuing linear debugging?

Escalate a blocked software workflow when complex debugging or planning exceeds standard linear capacity, requiring structured consensus generation to unblock inconclusive evidence and architectural decisions.

Can I use this multi-agent analysis for standard linear development tasks?

Multi-agent analysis is designed for complex verification challenges and architectural deadlocks, not standard linear workflows, preventing unnecessary intervention for routine software development tasks.

What's the best way to unblock contradictory evidence in a stalled software development task?

The best way to unblock contradictory evidence is applying a three-panel ensemble of primary, adversarial, and pragmatic agents to synthesize perspectives and generate consensus on the stalled task.