skills.rest
guardian-intelligence
guardian-intelligenceOFFICIAL
Explore all skills by this author →
Website𝕏@guardians_llcGitHub

ticket-queue

Orchestrate RFC-ticket processing with implementer dispatch and sequential merges to main.

1|Updated Jan 22, 2026
Search Tags:#workflow#GitHub#merge#queue#ticket#RFC
One-click install
npx skills add https://github.com/guardian-intelligence/apm2 --skill ticket-queue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket-queue
Source: https://github.com/guardian-intelligence/apm2/tree/main/documents/skills/ticket-queue
Command: npx skills add https://github.com/guardian-intelligence/apm2 --skill ticket-queue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Orchestrates end-to-end RFC-ticket processing by dispatching implementers, supervising progress, and merging tickets to main, reducing manual coordination and delays.

Core Features & Use Cases

  • Ticket selection and dependency checks across RFC tickets.
  • Background implementer subagents with lifecycle supervision until PRs merge.
  • Cadence-based monitoring of PR status, reviews, and CI signals for RFCs.

Quick Start

Use the ticket-queue skill to begin processing the next unblocked RFC ticket, then let the orchestrator dispatch, monitor, and loop until the ticket is merged.

Frequently Asked Questions about ticket-queue

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

FAQPage Schema
How do I automate sequential RFC ticket merges to main?▼

Automating sequential RFC ticket merges to main requires an orchestrator that selects unblocked tickets, dispatches implementer subagents, monitors CI and PR status, and enforces sequential merges. This loop-based control removes manual coordination delays.

How does background implementer dispatch work for GitHub ticket queues?▼

Background implementer dispatch for GitHub ticket queues works via task-based subagents that handle branch management and code changes. The orchestrator supervises their lifecycle and monitors PR status until the ticket merges to main.

Can I use GitHub CLI to monitor CI signals and PR reviews for RFC workflows?▼

Yes, you can use GitHub CLI to monitor CI signals and PR reviews for RFC workflows. The orchestrator performs cadence-based monitoring of PR status, reviews, and CI checks to determine merge readiness before proceeding.

What is the best way to handle dependency checks across multiple RFC tickets?▼

The best way to handle dependency checks across multiple RFC tickets is through a reference-driven decision tree that evaluates ticket states. The orchestrator selects the next unblocked ticket by verifying dependencies before dispatching implementers.

Does ticket-queue orchestration support loop-based workflow control for documents and work tickets?▼

Yes, ticket-queue orchestration supports loop-based workflow control for documents, work tickets, and RFC workflows. It iterates through ticket selection, dispatch, monitoring, and sequential merging until all queued items are resolved.

Related Skills

Explore More Software Engineering Skills→
eysenfalkeysenfalk

git-workflow

Enforce Git branch naming, commit message formats, and merge policies.

Community
Advanced
nand1234nand1234

rollback-ticket

Revert a ticket merge from the CP branch with validation and confirmation.

Community
Advanced
519lab519lab
2

github-pr-workflow

Automate GitHub Pull Request lifecycle with branch creation, CI monitoring, and merging.

Official
Intermediate
kevinnftkevinnft
13

github-pr-workflow

Coordinate GitHub pull request lifecycles from branch creation to merge.

Community
Advanced