pm-ticketing-integration

Detect ticket references and enforce ticket-driven delegation across agents.

Updated Mar 25, 2026

Search Tags:#workflow #integration #delegation #project-management #ticketing #ticket-id

Ready to run

npx skills add https://github.com/bobmatnyc/claude-mpm-marketplace --skill pm-ticketing-integration-bobmatnyc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pm-ticketing-integration
Source: https://github.com/bobmatnyc/claude-mpm-marketplace/tree/main/plugins/claude-mpm/skills/mpm-ticketing-integration
Command: npx skills add https://github.com/bobmatnyc/claude-mpm-marketplace --skill pm-ticketing-integration-bobmatnyc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ticket-driven coordination for software projects, ensuring work is always linked to a ticket and delegated to the correct agent, reducing context-switching and improving traceability.

Core Features & Use Cases

Ticket detection and context propagation across agents
Lifecycle steps: start work, progress updates, blockers, completion
Enforce delegation rules to ensure all ticket operations go through the ticketing agent

Quick Start

Refer to a ticket (e.g., PROJ-123) to initiate the TkDD workflow.

Frequently Asked Questions about pm-ticketing-integration

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

FAQPage Schema

How do I enforce ticket-driven development across my project management workflow?▼

Ticket-driven development is enforced by detecting ticket references like PROJ-123 or GitHub issues and routing all operations through a strict delegation agent. This ensures every task is linked to a ticket and assigned to the correct agent.

Can I use ticket references from GitHub issues and URLs to coordinate work?▼

Yes, ticket context is detected across multiple formats including GitHub issues, URL-based references, and standard ticket IDs like PROJ-123. The workflow propagates this context through research, engineering, and QA delegation steps.

What is the best way to manage blockers and progress updates in a ticketing workflow?▼

Blockers and progress updates are managed through a structured ticketing workflow lifecycle. The ticketing agent handles these stages by propagating ticket context and enforcing delegation rules to the appropriate specialized agents.

How do I start work on a ticket using a delegation workflow?▼

To start work, simply refer to a ticket such as PROJ-123 to initiate the workflow. The system detects the reference and begins coordinating the work through its lifecycle steps via the ticketing agent.

Why does my ticketing workflow require all operations to go through a ticketing agent?▼

All ticket operations go through the ticketing agent to enforce strict delegation rules and reduce context-switching. This guarantees that work remains traceable and correctly delegated to research, engineering, or QA agents.