
from paperclip61,043
Run a product-focused forensic investigation on stalled or looping issue trees, produce a root-cause write-up and an approval-gated remediation plan without shi
A repeatable, product-oriented forensic procedure for investigating stalled, looping, or over-recovered issue trees. The skill guides the agent to identify the exact stop-point, collect evidence (run ids, timestamps, transitions), survey recent related work, classify non-progressing issues, and frame a general product contract that preserves three invariants: productive work continues, only real blockers stop work, and no infinite loops. The output is a documented plan (phased, assigned, and approval-gated) rather than code changes.
Use this skill when an assignment or issue title/body explicitly asks "why did this work stop", "infinite loop", "liveness — what happened here", or when a user links a stalled/looping issue tree and requests forensics or a plan before any code changes. Do NOT use when the task asks to ship a code fix immediately.
The skill is implementation-agnostic but mentions typical agent roles (Codex/Claude/OpenClaw) for assignee suggestions in plans.
A well-structured diagnostic skill for investigating stalled/looping issue trees in paperclip.ai's internal workflow. The SKILL.md is thorough with clear triggers, anti-triggers, an 8-step procedure, pitfalls, and a verification checklist. No scripts to run or evaluate. Extremely niche — references internal PAP issue numbers, internal team roles, and internal document paths, making it largely inapplicable outside that specific organization.
Well-written procedural skill with excellent structure and clear anti-patterns. The three-invariants framework is a strong design choice. However, its usefulness is severely limited by deep ties to a specific organization's internal processes, issue tracker conventions, and team structure.