ticket

Coordinates engineering ticket workflows including RFCs, worktrees, and PRs via cargo xtask commands.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Engineers spend excessive time coordinating work on tickets, aligning RFCs, and managing PRs, leading to context switching and delays.

Core Features & Use Cases

  • Ticket orchestration: Manage new tickets and follow-ups for existing PRs, tying work to RFCs and test plans.
  • RFC linkage & requirements tracking: Connect tickets to RFCs and decomposition documents, ensuring traceability.
  • PR readiness automation: Bootstrap worktrees, enforce acceptance criteria, and prepare PRs with the ticket ID in the title.
  • Use Case: When a developer receives a new ticket, run the workflow to bootstrap a worktree, generate a ticket YAML, and push a PR referencing the ticket.

Quick Start

Start the ticket workflow for a new ticket using the start-ticket command, for example: cargo xtask start-ticket TCK-XXXXX

Frequently Asked Questions about ticket

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

FAQPage Schema
How do I automate ticket-driven engineering workflows from ticket creation to PR?

Ticket-driven engineering workflows are automated by orchestrating ticket creation, RFC linkage, worktree bootstrapping, and PR preparation through cargo xtask commands like start-ticket, push, and commit.

How do I link an RFC to a development ticket for requirements traceability?

Link an RFC to a development ticket by connecting the ticket to the RFC and decomposition documents, ensuring traceability and alignment between engineering work and design requirements throughout the workflow.

Can I use cargo xtask to bootstrap a worktree for a new ticket?

Yes, cargo xtask supports worktree bootstrapping for a new ticket by running the start-ticket command with a ticket ID like TCK-XXXXX, which generates a ticket YAML and prepares the development environment.

Does PR readiness automation enforce acceptance criteria before pushing?

PR readiness automation enforces acceptance criteria by preparing PRs with the ticket ID in the title, tying work to RFCs and test plans, and ensuring requirements are met before pushing commits.

What is the best way to manage follow-up work for existing PRs in a ticket queue?

Manage follow-up work for existing PRs by running the ticket workflow within a ticket queue, which extracts ticket context, aligns RFCs, and coordinates subsequent push and commit operations.

Do I need a ticket YAML file to coordinate RFC alignment and PR workflows?

A ticket YAML file is generated during the workflow to capture ticket context, enforce acceptance criteria, and drive automated PR workflows, ensuring proper RFC alignment and traceability.