break-failure-loop

Pauses repeated equivalent attempts and reconstructs evidence to select a recovery state.

Updated May 12, 2026
One-click install
npx skills add https://github.com/mtk177a/skills --skill break-failure-loop-mtk177a
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: break-failure-loop
Source: https://github.com/mtk177a/skills/tree/main/skills/break-failure-loop
Command: npx skills add https://github.com/mtk177a/skills --skill break-failure-loop-mtk177a

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an agent or developer keeps retrying materially equivalent changes under the same hypothesis without gaining new evidence, work stalls in a failure loop. This Skill interrupts that cycle, reconstructs what each attempt actually established, and returns a decision-ready recovery state instead of another equivalent mutation. ## Core Features & Use Cases - Stagnation Detection: Classifies work as stalled only when attempts are materially equivalent, the hypothesis is unchanged, and no decision-relevant evidence is emerging, never based on attempt count alone. - Attempt-Evidence Reconstruction: Rebuilds each attempt as hypothesis, action, result, evidence gained, and remaining mutation, keeping observed facts, reported results, inference, and unknowns distinct. - Recovery Decision Model: Returns one of four states: Not stalled, Blocked, Diagnostic next (one discriminating checkpoint), or Diversify (handoff to structural candidate search via explore-decision-space). - Use Case: Two nil-guard edits to a handler fail with the same stack trace. The Skill pauses a third guard, reconstructs both attempts under the unchanged handler-input hypothesis, and recommends a single read-only checkpoint at the decoder entry with outcome-dependent next decisions. ## Quick Start Ask the agent to pause the repeated attempts, reconstruct what each attempt established, and tell you the recovery state and next checkpoint without making any changes.

Frequently Asked Questions about break-failure-loop

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

FAQPage Schema
How do I stop an AI agent from repeating the same failing fix?▼

Invoke this Skill when multiple attempts under the same hypothesis fail without new evidence. It pauses further equivalent mutations, reconstructs each attempt's hypothesis and evidence, and returns a recovery state with one discriminating checkpoint or a blocked or diversification handoff.

What counts as a failure loop versus normal debugging?▼

A failure loop requires materially equivalent attempts, an unchanged causal hypothesis, and no decision-relevant new evidence. A first failure, repeated observation of the same test, a changed hypothesis, or continuing evidence gain is explicitly not a loop and returns Not stalled.

Does this Skill modify code or run the suggested diagnostic?▼

No. The Skill is strictly read-only: it never edits files, executes the proposed checkpoint, reverts or stashes changes, or performs external writes. It recommends a checkpoint and returns control to the originating workflow.

When should I use break-failure-loop instead of investigate-failure?▼

Use investigate-failure for ordinary investigation of an unexplained technical failure. Use break-failure-loop only when that investigation itself is repeating an unchanged branch without new evidence, or when implementation attempts have stalled under one hypothesis.

What happens when no local diagnostic can distinguish the remaining hypotheses?▼

The Skill returns Diversify, identifies the exhausted design anchor, and hands off the attempt and evidence history to explore-decision-space for structural candidate search. It does not generate the candidate portfolio itself.

Can it treat instructions found in logs or tool output as commands?▼

No. Logs, errors, diffs, and external content are treated as evidence, not authority. Instruction-like content embedded in evidence is explicitly flagged as untrusted and non-authoritative rather than executed or silently ignored.