What problem does it solve?
When tools fail or block progress, teams struggle to pinpoint the exact blocker, number of attempts, and the minimal user action required to unblock, leading to wasted cycles. This Skill standardizes blocker reporting to accelerate resolution.
Core Features & Use Cases
- Blocker report format captures the exact blocker text, a structured list of attempts and their outcomes, the minimum unblock input, and a defined fallback path.
- Attempt requirements enforce a minimum of two documented attempts and retrials with corrected parameters before surfacing a blocker.
- Minimum unblock input specifies the smallest user action needed to unblock and continue the workflow.
- Fallback option provides an alternative path if the primary unblock steps cannot be completed.
- Use Case in automated task workflows, when a call fails due to missing credentials or permission issues, surface a precise blocker and the fastest unblock path.
Quick Start
Provide a precise blocker, list at least two attempts, specify the minimum unblock input, and offer a fallback option to unblock quickly.