diagnose-why-work-stopped
Diagnose stalled, looping, or over-recovered Paperclip issue trees and propose a no-code product-rule plan. Use when asked why work stopped, why it looped, or how to prevent a tree from going too deep.
Install
git clone https://github.com/paperclipai/paperclip /tmp/paperclip && ln -s /tmp/paperclip/.agents/skills/diagnose-why-work-stopped ~/.claude/skills/diagnose-why-work-stoppedFrom README
Diagnose Why Work Stopped A repeatable procedure for the recurring class of issues where the user (or a manager) points at a stalled / looping / over-recovered issue tree and asks "why did this stop / why is this looping / how do we make sure this doesn't happen again?" This skill is diagnostic + product-design, not engineering. The output is a written root cause and an approved plan. No code changes leave this skill. Canonical execution model: read doc/execution-semantics.md before diagnosing or proposing a new liveness/recovery rule. Use that document as the source of truth for status, action-path, post-run disposition, bounded continuation, productivity review, pause-hold, watchdog, and explicit recovery semantics. If the investigation finds a true product-rule gap, the plan should say whether doc/execution-semantics.md needs a matching update.
More from this repo
paperclip
Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating...
paperclip-create-agent
Used to create new agents in Paperclip with governance-aware hiring.
paperclip-create-plugin
Used to create and develop external Paperclip plugins with the CLI-first workflow.