blocker-supervisor-unblocker

Resolve technical blockers using browser tools, terminal commands, and playbooks.

4|Updated Dec 7, 2025
One-click install
npx skills add https://github.com/grigb/gas-prompt-library --skill blocker-supervisor-unblocker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blocker-supervisor-unblocker
Source: https://github.com/grigb/gas-prompt-library/tree/main/agents/agent-blocker-supervisor-unblocker
Command: npx skills add https://github.com/grigb/gas-prompt-library --skill blocker-supervisor-unblocker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the operational bottleneck of managing and resolving technical blockers within a complex agent ecosystem, preventing manual oversight and stalled project workflows.

Core Features & Use Cases

  • Atomic Resolution: Automatically claims and resolves idle blockers using browser MCP tools, terminal commands, and on-disk playbooks.
  • Intelligent Filtering: Supports workstream-scoped operations to ensure blockers are resolved within the correct project context.
  • Safety Guardrails: Enforces strict separation between resolution and project implementation, ensuring that only verified outcomes are recorded.

Quick Start

Invoke the blocker unblocker to scan the master index and resolve the highest priority idle blocker for the current workstream.

Frequently Asked Questions about blocker-supervisor-unblocker

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

FAQPage Schema
How do I automate the resolution of technical blockers in a multi-agent system?

Automating blocker resolution involves orchestrating browser tools, terminal commands, and predefined playbooks within a multi-agent system. The process claims and clears idle blockers per-cycle while enforcing strict workstream-scoped filters and non-destructive project interaction.

What is atomic state transition when resolving system blockers?

Atomic state transition ensures blockers are claimed and resolved individually without partial updates. The system enforces strict separation between resolution actions and project implementation, guaranteeing only verified outcomes are recorded.

How do I scope blocker resolution to specific project workstreams?

You scope resolutions by applying intelligent workstream filters during the orchestration process. This ensures the system only resolves idle blockers within the correct project context, preventing cross-project interference and maintaining operational focus.

Does the blocker unblocker modify project files during the resolution process?

No, it enforces non-destructive project interaction through strict safety guardrails. It separates the resolution process from project implementation entirely, ensuring that only verified resolution outcomes are recorded without altering source code.

What's the best way to handle operational bottlenecks and stalled workflows in an agent ecosystem?

The best approach is orchestrating automated per-cycle scans of a master index to resolve high-priority idle blockers. This prevents manual oversight and automatically clears stalled project workflows within complex agent ecosystems.