dispatch-plan-closeout

Close shared dispatch plan issues after PRs, approvals, and audit pass.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/graysurf/agent-runtime-kit --skill dispatch-plan-closeout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dispatch-plan-closeout
Source: https://github.com/graysurf/agent-runtime-kit/tree/main/tests/golden/claude/plugins/dispatch/skills/dispatch-plan-closeout/expected
Command: npx skills add https://github.com/graysurf/agent-runtime-kit --skill dispatch-plan-closeout

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Close a shared dispatch plan issue after lane PRs, review, validation, integration, approval, and the strict dispatch close-ready audit pass.

Core Features & Use Cases

  • Enforces preflight checks by ensuring all lane PRs are merged and approvals present.
  • Coordinates run-state validation and dashboard repair when stale.
  • Posts a final closeout update and transitions labels from state::needs-triage to state::closed.

Quick Start

Initiate the plan-issue closeout sequence with linked PRs and approvals, then record the dashboard repair if needed and finalize the close.

Frequently Asked Questions about dispatch-plan-closeout

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

FAQPage Schema
How do I close a dispatch plan after multiple pull requests are merged?

To close a dispatch plan, initiate the closeout sequence after all lane PRs are merged and approvals are collected. The workflow performs a strict close-ready audit, handles dashboard repair if stale, posts a final update, and transitions issue labels from state::needs-triage to state::closed.

What is a dispatch plan close-ready audit?

A dispatch plan close-ready audit is a strict preflight validation that ensures all lane PRs are merged, approvals are collected, and run-state is verified. It also checks dashboard state and coordinates repair when stale before allowing the final closeout mutation.

How do I coordinate multi-lane dispatch plan approvals and dashboard repair?

Multi-lane dispatch plan coordination enforces preflight checks for linked-PR binding and approval evidence collection. It validates run-state and automatically coordinates dashboard repair when stale data is detected during the closeout workflow.

Can I use this workflow for teams managing multiple PRs across dashboards?

Yes, this workflow is designed for teams coordinating multi-lane dispatch plans across multiple PRs, dashboards, and approvals. It handles preflight checks, dashboard repair, and final label transitions within the Codex or Claude style workflow context.

Why does my dispatch plan workflow fail the closeout mutation?

The dispatch plan closeout fails if preflight checks detect unmerged lane PRs, missing approval evidence, or invalid run-state validation. Stale dashboards may also block the closeout mutation until coordinated dashboard repair is completed.