diagnose-why-work-stopped
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.
- Installs
- 182
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/paperclipai/paperclip --skill diagnose-why-work-stopped- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads diagnose-why-work-stopped automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Diagnose Why Work Stopped
Use Fix Failed Paperclip Run. 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, read the current doc/execution-semantics.md, 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:
- Productive work has a real next action and owner.
- Only genuine blockers stop work, including approval, credentials, and budget.
- 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.
FAQ
What does the diagnose-why-work-stopped skill do?
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.
How do I install diagnose-why-work-stopped?
Run npx skills add https://github.com/paperclipai/paperclip --skill diagnose-why-work-stopped in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/diagnose-why-work-stopped/ (personal) or .claude/skills/diagnose-why-work-stopped/ (project).
Which AI agents can use diagnose-why-work-stopped?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is diagnose-why-work-stopped safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains diagnose-why-work-stopped?
It is published by paperclipai in paperclipai/paperclip. It has 182 recorded installs.
More from paperclipai/paperclip
paperclip
paperclipai/paperclip
Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.
paperclip-create-agent
paperclipai/paperclip
Create new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hire request.
paperclip-create-plugin
paperclipai/paperclip
Create and develop external Paperclip plugins with the CLI-first workflow. Use when scaffolding a plugin, iterating on a local plugin, installing it into Paperclip, or updating plugin authoring docs.
para-memory-files
paperclipai/paperclip
Use a file-based PARA memory system to store, retrieve, and organize durable knowledge across sessions. Trigger on saving facts, daily notes, entity records, weekly synthesis, recall, tacit user patterns, or plan memory.
create-agent-adapter
paperclipai/paperclip
Open the skill to read its SKILL.md instructions.
Popular testing & qa skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
grilling
mattpocock/skills
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
migrate-to-shoehorn
mattpocock/skills
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
run-train
lllllllama/rigorpilot-skills
Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized trainoutputs/. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.
test-driven-development
obra/superpowers
Use when implementing any feature or bugfix, before writing implementation code
finishing-a-development-branch
obra/superpowers
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work