global-triage

Route owner input to project-local work-order queues via registry analysis.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the fragmentation of owner input across multiple AI agent projects by providing a single, portfolio-wide intake and routing mechanism.

Core Features & Use Cases

  • Unified Intake: Captures owner requests from any thread and resolves them to the correct project queue.
  • Intelligent Routing: Uses a project registry to identify the target project and creates standardized work orders.
  • Use Case: When you have multiple active projects, use this Skill to capture a new idea or task in one place and ensure it is automatically routed to the correct project's work-order queue without manual intervention.

Quick Start

Use the global triage skill to capture my request to update the project documentation and route it to the appropriate project queue.

Frequently Asked Questions about global-triage

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

FAQPage Schema
How do I centralize task intake and routing for multiple AI agent projects?

Centralized task intake and routing captures owner requests from any thread and uses a project registry to resolve them to the correct project-local work-order queue automatically. This prevents fragmented inputs across multiple active projects.

How does centralized work order routing handle duplicate detection and provenance?

Centralized work order routing handles duplicate detection by checking incoming requests against existing entries before queuing. It maintains a global provenance ledger to ensure non-destructive routing and traceability across all portfolio projects.

What's the best way to route owner input to specific project queues in a multi-agent orchestration environment?

The best way to route owner input in multi-agent orchestration is using a portfolio-scope intake mechanism that analyzes a project registry, identifies the target project, and creates standardized work orders without manual intervention.

Can I capture new ideas from any thread and automatically route them to the correct project queue?

Yes, you can capture new ideas or tasks from any thread. The routing mechanism resolves the target project automatically and queues the standardized work order, eliminating the need for manual project assignment.

Do I need a project registry to maintain centralized intake for my portfolio?

Yes, a project registry is required for centralized intake. The routing mechanism relies on registry analysis to accurately resolve incoming owner requests and direct them to the appropriate project-local work-order queues.

When should I not use centralized portfolio-wide intake and routing?

Centralized portfolio-wide intake and routing is not suitable for single-project environments or workflows lacking a project registry. Without multiple active projects requiring standardized work orders, the orchestration overhead provides no benefit.