diagnose-why-work-stopped

Analyze task trees to identify causes of work stoppages, loops, or recoveries.

Updated May 4, 2026
One-click install
npx skills add https://github.com/o9nn/entelechorg --skill diagnose-why-work-stopped-o9nn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose-why-work-stopped
Source: https://github.com/o9nn/entelechorg/tree/main/skills/diagnose-why-work-stopped
Command: npx skills add https://github.com/o9nn/entelechorg --skill diagnose-why-work-stopped-o9nn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a diagnostic procedure to analyze issues where work has stopped, looping, or over-recovered, enabling teams to identify root causes and plan effective resolutions.

Core Features & Use Cases

  • Root Cause Analysis: Investigates stalled or looping task trees based on issue metadata and execution history.
  • Checklist & Classification: Classifies issues as needing human intervention, being agent-actionable, or already covered by existing processes.
  • Use Case: When a task causes infinite loops or mysterious stoppages, this Skill guides the analysis and preparation of an intervention plan, reducing downtime and improving reliability.

Quick Start

Trigger this skill to diagnose issues that are preventing progress in a project or workflow.

Frequently Asked Questions about diagnose-why-work-stopped

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

FAQPage Schema
How do I diagnose the root cause of a stalled or looping task tree?

To diagnose stalled or looping task trees, analyze recent issue metadata and execution history to identify the exact cause of work stoppages and prepare an intervention plan.

Why does my workflow task get stuck in an infinite loop?

Workflow tasks enter infinite loops due to execution state errors or unresolved dependencies. Analyzing the complex task tree based on recent issue history identifies the specific trigger.

What is the best way to analyze over-recovered tasks in operational troubleshooting?

The best way to analyze over-recovered tasks is to apply a diagnostic procedure that classifies issues based on execution history and maintains bounded recovery invariants.

When do I need task diagnostics for AI-driven workflows?

You need task diagnostics for AI-driven workflows when mysterious stoppages or infinite loops prevent progress, requiring issue classification and root cause analysis to restore productivity.

How do I classify if a stalled task needs human intervention or is agent-actionable?

You classify stalled tasks by analyzing issue metadata and execution history to determine if the stoppage requires human intervention, is agent-actionable, or is covered by existing processes.