diagnose-why-work-stopped

Diagnose stalled or looping Paperclip issue trees and produce approved product-rule plans.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/adamtpang/summon.company --skill diagnose-why-work-stopped-adamtpang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose-why-work-stopped
Source: https://github.com/adamtpang/summon.company/tree/main/.agents/skills/diagnose-why-work-stopped
Command: npx skills add https://github.com/adamtpang/summon.company --skill diagnose-why-work-stopped-adamtpang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an AI agent team stalls, loops infinitely, or recovers work too aggressively, managers need a root cause and a durable product rule rather than a one-off patch. This Skill provides a repeatable forensic procedure that identifies the exact stop point in an issue tree and turns it into an approved, phased plan. ## Core Features & Use Cases - Tree forensics: Walks the linked issue, its blocker chain, recovery siblings, and recent runs to pinpoint the exact issue and state combination that stopped progress, quoting run ids and comment timestamps as evidence. - Invariant-checked rule design: Frames every fix as a general product contract that preserves three invariants: productive work continues, only real blockers stop work, and no infinite loops. - Approval-gated planning: Writes a phased plan into the issue's plan document, opens a request_confirmation interaction, and only decomposes into child issues after board or CTO acceptance. - Use Case: A manager links a stalled issue tree and asks why it stopped. The Skill walks the tree, finds an in_review leaf with no execution participant, surveys recently shipped liveness work, and proposes a contract update to doc/execution-semantics.md with phased implementation issues. ## Quick Start Ask the agent to diagnose why the linked Paperclip issue tree stopped working and produce a root-cause write-up with a proposed product rule before any code changes.

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 why an AI agent issue tree stopped working?

Walk the linked issue, its blocker chain, parents, recovery siblings, and recent runs node-by-node to find the exact issue and state combination that stops progress. Quote run ids and comment timestamps as evidence before proposing any rule.

How do I prevent infinite loops in stranded-work recovery?

Bound continuation and recovery loops so they are distinguishable from productive continuation, and ensure recovery never treats its own recovery issues as recoverable source work. Detect recursive recovery patterns and refuse to deepen them.

When should I use this diagnostic skill instead of normal debugging?

Use it when asked why work stalled, looped, or recovered too deeply, or when forensics and a product rule are requested before any change. Do not use it for direct code fixes, ordinary bug reports, or fixing your own implementation bug.

Can this skill ship code changes to fix a stalled tree?

No. The skill is diagnostic and product-design only: it produces a written root cause and a phased plan, opens a request_confirmation interaction, and creates child issues only after board or CTO approval.

What happens when the stalled issue is in another company scope?

Cross-company forensics must respect API scoping. If the agent token returns 403, request a board-approved diagnostic path or proceed from inferred evidence and explicitly label those claims as provisional.