paperclipai/paperclip / .agents/skills/diagnose-why-work-stopped
diagnose-why-work-stopped
VerifiedCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.8 KB |
SKILL.md
View on GitHub---
name: diagnose-why-work-stopped
description: Compatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.
---
# Diagnose Why Work Stopped
Use [Fix Failed Paperclip Run](../fix-failed-paperclip-run/SKILL.md). It owns the current
workflow: find the first causal failure, reproduce it red, repair the shared
contract, test second-order effects, verify the real workflow, and deliver a PR
with passing checks. A normal request to fix stopped work continues through that
workflow without a separate plan-approval gate.
If the user or calling workflow explicitly asks for diagnosis only or requires
approval before implementation, perform the investigation and safety analysis
within that scope. For example, a Terminal-Bench diagnosis child does not override
the loop's board approval boundary. Keep the next action and its owner explicit.
For issue-tree diagnosis, inspect the
relevant subtree and recent repairs, and classify non-progressing nodes:
- **Genuine wait:** a named human or external dependency must act.
- **Agent-actionable but unrouted:** authorized useful work lacks a live path.
- **Already covered:** existing work owns the next action; do not duplicate it.
Preserve these three invariants together:
1. Productive work has a real next action and owner.
2. Only genuine blockers stop work, including approval, credentials, and budget.
3. Recovery is bounded and cannot recursively recover itself.
Frame any repair as a general behavioral contract, check it against a productive
counterexample, and follow the new skill through the authorized finish line.
Historical task links and private incident access are not required.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| garden-inboxpaperclipai/paperclipScan a Paperclip user's Mine inbox, classify reversible archive candidates, request checkbox confirmation, and archive only accepted selections. Use when asked to garden, clean up, prune, or tidy a Paperclip inbox without changing issues, branches, or workspaces. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |