dispatch

Route GitHub issues to the correct teammate after validating readiness, dependencies, and ownership.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/lucas42/lucos_claude_config --skill dispatch-lucas42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dispatch
Source: https://github.com/lucas42/lucos_claude_config/tree/main/skills/dispatch
Command: npx skills add https://github.com/lucas42/lucos_claude_config --skill dispatch-lucas42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guardrails and automation for routing a GitHub issue to the correct implementation teammate, ensuring readiness, dependencies, and ownership are verified before assignment.

Core Features & Use Cases

  • Issue triage and routing: validate issue ownership, read the body and comments to determine readiness for work.
  • Dependency and PR checks: detect and verify cross-repo blockers and PR status to avoid dispatching blocked work.
  • Estate-rollout awareness: identify whether the issue requires an estate-wide rollout workflow and route accordingly.
  • Automated notification: ping the designated teammate with the exact issue URL to begin work without summarizing the ticket.

Quick Start

Provide the issue URL (or run /next to populate it) and run dispatch to assign the task to the appropriate teammate.

Frequently Asked Questions about dispatch

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

FAQPage Schema
How do I automate routing GitHub issues to the correct teammate?

Automated GitHub issue routing parses the issue URL, fetches the body and comments, evaluates project-board ownership, and sends a direct notification with the URL to the assigned teammate. This dispatch process assigns tasks only after verifying readiness and dependencies.

What is issue triage and how does dependency checking work before assignment?

Issue triage validates ownership and reads ticket bodies and comments to determine readiness. Dependency checking detects and verifies cross-repo blockers and PR status to avoid dispatching work that is currently blocked.

Can I use this dispatch automation for estate-wide rollout workflows across projects?

Yes, the dispatch automation identifies whether an issue requires an estate-wide rollout workflow across projects and routes the task accordingly. It evaluates project-board ownership to ensure the issue reaches the correct implementation teammate.

How do I start assigning GitHub issues using this automated triage tool?

To start automated triage, provide the GitHub issue URL or run the /next command to populate it, then execute the dispatch function. The tool validates readiness, dependencies, and ownership before pinging the designated teammate.

What limitations exist when dispatching blocked GitHub issues to teammates?

The dispatch process will not route issues with unresolved cross-repo blockers or failing PR readiness checks. It acts as a guardrail to prevent assigning blocked work, ensuring teammates only receive verified, actionable issue URLs.

Does the dispatch notification summarize the GitHub ticket for the assigned teammate?

No, the dispatch automation sends a direct notification containing only the exact issue URL to the assigned teammate. It does not summarize the ticket body or comments, ensuring the teammate reviews the original issue directly.