diagnose-why-work-stopped Skill
How to handle "why did this work stop / why is this looping?" assignments. Forensics first on the named tree, surface the exact stop-point, frame the fix as a general product rule that respects three invariants (productive work continues, only real blockers stop work, no infinite loops), and deliver a plan — no code ch Published by microsoft in amplifier-app-paperclip.
What is diagnose-why-work-stopped Skill?
How to handle "why did this work stop / why is this looping?" assignments. Forensics first on the named tree, surface the exact stop-point, frame the fix as a general product rule that respects three invariants (productive work continues, only real blockers stop work, no infinite loops), and deliver a plan — no code ch Published by microsoft in amplifier-app-paperclip. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Design and media
- Design and media use cases
Technical details
- Install or run with Copy skill directory
When to use diagnose-why-work-stopped Skill
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/amplifier-app-paperclip
- Skill file: skills/diagnose-why-work-stopped/SKILL.md
What it does
How to handle "why did this work stop / why is this looping?" assignments. Forensics first on the named tree, surface the exact stop-point, frame the fix as a general product rule that respects three invariants (productive work continues, only real blockers stop work, no infinite loops), and deliver a plan — no code ch
Skill instructions
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. When to use Trigger on an assignment whose title or body matches any of: - "why did this work stop", "why did this stall", "why did this jus
Explore related resources
Frequently asked questions
What is diagnose-why-work-stopped?
diagnose-why-work-stopped is a open-source AI agent skill with Copy skill directory. How to handle "why did this work stop / why is this looping?" assignments.
Who is diagnose-why-work-stopped best for?
diagnose-why-work-stopped is best for reusing agent instructions, scripts, and references, design and media workflows.
How do I install diagnose-why-work-stopped?
Install or run diagnose-why-work-stopped using Copy skill directory. Check diagnose-why-work-stopped for the latest setup command.
Is diagnose-why-work-stopped actively maintained?
diagnose-why-work-stopped may need a closer maintenance check before production use.
Auto-fetched from GitHub.
