Generate a structured handoff report with four sections when progress stalls.
npx skills add https://github.com/danmestas/wardrobe --skill stuck-detector
Please help me install this Agent Skill. Skill: stuck-detector Source: https://github.com/danmestas/wardrobe/tree/main/skills/stuck-detector Command: npx skills add https://github.com/danmestas/wardrobe --skill stuck-detector
The off-ramp for stalled conversations. When the agent or the user realizes the current path isn’t progressing, this skill stops the retry loop and produces a structured handoff so progress can resume in a fresh session.
Activate the stuck-detector to generate a concise handoff report and pause the session.
High-intent search queries and answers about installing and using this skill.
To stop an agent retry loop when stuck mid-task, you need a structured handoff mechanism that halts retries and generates a report. This skill identifies the stall, stops the loop, and creates a handoff document so progress can resume in a fresh session.
A structured handoff report for workflow escalation is a document capturing what was attempted, what failed, and what information is needed to unblock progress. It enables seamless context transfer to a fresh session, another user, or an escalated support tier.
To generate a mid-task handoff report when a workflow stalls, activate the stuck-detector skill. It automatically saves a markdown file to ~/.claude/evolution-reports/ containing the original ask, failed attempts, unblocking requirements, and recommended next actions.
Yes, you can resume a stalled agent session after generating a handoff report. The skill prompts you to choose between continuing with a reduced scope, escalating the issue, or pausing the session entirely, giving you full control over the next workflow step.
An escalation handoff for a stalled agent must include the original ask, what was tried and failed, what specific information would unblock progress, and a recommended next action. This structured format ensures the receiving session or user has immediate context.
You should use a stuck detector when the current workflow path is no longer progressing and retries are failing. It provides an off-ramp for stalled conversations by stopping the loop and producing a structured handoff rather than wasting resources on repeated attempts.
charly3pinsTrace errors backward through call stacks to identify original triggers.
corygabrielsenGenerates a Fork Ready summary and terminal command for a new Claude session.
AtyantikApply task-specific templates to structure AI coding sessions.
hamzaPixlCapture session decisions and generate handoff documents from Git state.
