blocker-escalation-report

To generate a blocker escalation report, trigger this skill when progress stalls to capture context, blocker type, and required inputs into a standardized artifact for human review. It produces a structured exit path with re-routing guidance and telemetry summary.

A blocker escalation report is used to document and escalate unresolved blockers, missing context, or unresolvable decisions in a multi-agent workflow. It serves as a terminal artifact that surfaces necessary information to human operators for accountability and next steps.

You should create an escalation report when a review cycle reaches an escalation point, lacks required context, or faces unresolvable decisions. It provides a structured exit path to trigger human input or re-routing without stalling the workflow indefinitely.

A blocker escalation report includes metadata sections for blocker type, required input, suggested rerouting, and telemetry. This structure ensures the artifact captures all necessary context to enable timely human intervention and accountability.

Yes, this skill applies to review cycles reaching escalation points or unresolvable decisions. It generates a structured artifact that documents the blocker and produces a summary to enable re-routing or human operator input.

No, this blocker escalation report skill has no dependencies or components. It functions independently to produce standardized escalation artifacts and telemetry summaries for stalled workflow subtasks.