pm-ticketing-integration

Detect ticket IDs and URLs to automate task transitions and progress updates.

Updated Jan 30, 2026

Search Tags:#automation #workflow #development #project management #integration #ticketing

Ready to run

npx skills add https://github.com/MacPhobos/research-mind --skill pm-ticketing-integration

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the integration between project management ticketing systems and development workflows, ensuring seamless tracking and communication throughout the development lifecycle.

Core Features & Use Cases

Ticket Detection: Automatically identifies ticket IDs and URLs in conversations.
Workflow Automation: Executes predefined tasks for starting work, updating progress, reporting blockers, and completing tickets.
Context Propagation: Ensures all agent interactions include relevant ticket context.
Use Case: When a user mentions "Work on ticket PROJ-123", this Skill will automatically transition the ticket to 'in_progress', add a comment, and then delegate further research or development tasks to other agents while maintaining ticket context.

Quick Start

Use the pm-ticketing-integration skill to start work on ticket PROJ-123.

Frequently Asked Questions about pm-ticketing-integration

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

FAQPage Schema

How do I automate ticket-driven development workflows?▼

Ticket-driven development workflows are automated by detecting ticket IDs and URLs in conversations to trigger task transitions, progress updates, and blocker reporting across project management systems.

How do I transition a project management ticket to in progress automatically?▼

Tickets transition automatically when the integration detects a ticket ID or URL in a conversation, triggering predefined workflow tasks like starting work, adding comments, and updating progress.

How does ticket context propagation work in agent communications?▼

Ticket context propagation works by ensuring all agent interactions include relevant ticket information, allowing agents to delegate research or development tasks while maintaining the original ticket context.

Can I use this integration to report blockers on development tickets?▼

Yes, blocker reporting is a core workflow automation feature that automatically updates ticketing systems with blocker statuses when issues are detected during development tasks.

Do I need a specific project management platform to automate ticket transitions?▼

The integration connects with project management ticketing systems generically, requiring only ticket IDs or URLs to automate task transitions and workflow updates across supported platforms.

What are the limitations of automating ticket workflows through conversation detection?▼

The automation relies on detecting ticket IDs and URLs in conversations, so workflows cannot trigger without explicit ticket references and require predefined task configurations for each transition type.