blocker-supervisor-cataloger

Scans registered projects to catalog and index blocker artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of maintaining visibility across complex, multi-project environments by automatically scanning for blockers, maintaining project-specific indexes, and generating a master portfolio-level status report.

Core Features & Use Cases

  • Automated Scanning: Iterates through registered projects to identify and catalog blockers without manual intervention.
  • Portfolio Synchronization: Maintains a centralized master index and dashboard data, ensuring the human supervisor has a real-time view of all project impediments.
  • Lifecycle Management: Automatically ages stale blockers and releases expired claims, keeping the blocker registry clean and actionable.

Quick Start

Invoke the blocker cataloger to scan all registered projects and refresh the master index.

Frequently Asked Questions about blocker-supervisor-cataloger

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

FAQPage Schema
How do I automate blocker scanning across multiple project directories?

Maintain a master portfolio index by running automated cross-project blocker scans that synchronize project-specific data into a centralized dashboard. The cataloger operates in read-only discovery mode to refresh the master index.

Can I manage blocker staleness and claim expiration automatically across a portfolio?

A project registry integration is required to map directories for scanning. The blocker cataloger depends on this registry to iterate through projects and maintain consistent cross-project reporting.

What's the best way to maintain a centralized master index of project blockers?

Automate blocker scanning by using a cataloger skill that iterates through registered project directories to identify and catalog blocker artifacts. It generates a master portfolio-level index and maintains per-project status visibility.

Do I need a specific project registry to catalog blockers across multiple projects?

The blocker cataloger operates strictly in read-only discovery mode. It identifies and indexes blocker artifacts without modifying the original project files, ensuring safe cross-project portfolio scanning.

How does read-only discovery mode work for cross-project blocker indexing?

Manage blocker staleness and claim expiration automatically by invoking a cataloger that ages stale blockers and releases expired claims. This lifecycle management keeps the cross-project blocker registry clean and actionable.