skills.rest
xaionaro
xaionaroCOMMUNITY
Explore all skills by this author →
GitHub

blocker-resolution-protocol

Log blocker attempts, analyze causes, and route decisions through an internal resolution protocol.

Updated May 4, 2026
Search Tags:#workflow#escalation#blocker#review-loop#unblock#ate#eci
One-click install
npx skills add https://github.com/xaionaro/.config-codex --skill blocker-resolution-protocol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: blocker-resolution-protocol
Source: https://github.com/xaionaro/.config-codex/tree/main/skills/blocker-resolution-protocol
Command: npx skills add https://github.com/xaionaro/.config-codex --skill blocker-resolution-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When progress is blocked and review loops cannot converge, this protocol provides a formal, traceable path to identify, log, and resolve blockers, escalating to users as needed.

Core Features & Use Cases

  • Structured blocker recording: requires an attempt log with evidence across genuine, protocol-limit, and user-owned blockers.
  • Multi-role unblocking workflow: uses brainstormer, explorer, feasibility validator, and route steps to generate and evaluate internal paths.
  • Escalation-ready reporting: captures context, decisions, and remaining blockers to escalate to the user when no feasible path remains.
  • Use Case: applies to stalled review loops, ECI/ATE progress blocks, or lifecycle-control blockers that require user input or outside confirmation.

Quick Start

Initiate the blocker resolution protocol when a blocker is reported and escalate to the user if no feasible path remains.

Frequently Asked Questions about blocker-resolution-protocol

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve stalled work blockers when a code review loop cannot converge?▼

To resolve stalled work blockers, a structured escalation protocol logs attempts, analyzes blockers, and routes decisions. It enforces a genuine blocker record and escalates only when no feasible internal path remains.

What is the best way to unblock an ECI or ATE work-progress flow that has stalled?▼

To unblock a stalled ECI or ATE work-progress flow, apply a multi-role workflow using brainstormer, explorer, and feasibility validator steps to generate and evaluate internal paths before escalating.

When should I escalate a blocker to the user instead of continuing to retry internally?▼

You should escalate a blocker to the user only when no feasible internal path remains. The protocol tracks rejection and retry events, ensuring escalation happens solely after internal paths are exhausted.

How does a structured blocker resolution protocol handle lifecycle-control blockers?▼

A structured blocker resolution protocol handles lifecycle-control blockers by logging attempts with evidence and capturing context, decisions, and remaining blockers to escalate for outside confirmation when needed.

What evidence is required to record a genuine blocker before considering a stop-hook bypass?▼

Recording a genuine blocker before considering a stop-hook bypass requires an attempt log with evidence across genuine, protocol-limit, and user-owned blocker categories to validate the escalation.

Related Skills

Explore More Software Engineering Skills→
bybren-llcbybren-llc
395

agent-coordination

Coordinate specialist-agent assignments and escalate blockers in multi-agent workflows.

Official
Advanced
hadpadrahulhadpadrahul

gsd-pause-work

Capture current phase, progress, decisions, blockers, and remaining tasks in a timestamped continuation file.

Community
Intermediate
iamtouchskyeriamtouchskyer
189

opc

Coordinate a multi-agent digraph review pipeline with gate verdicts.

Community
Advanced
shin0720shin0720

auto-status

Aggregates SPEC statuses from a main project and its submodules into a unified dashboard view.

Community
Intermediate