discover-ticket

Analyze ticket overlaps to decide whether to create, merge, or split.

1|Updated Jan 15, 2026

Search Tags:#repository #split #merge #tickets #analyze #overlap #duplicate

Ready to run

npx skills add https://github.com/qmu/workaholic --skill discover-ticket

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: discover-ticket
Source: https://github.com/qmu/workaholic/tree/main/plugins/core/skills/discover-ticket
Command: npx skills add https://github.com/qmu/workaholic --skill discover-ticket

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams quickly determine whether a proposed ticket should proceed, merge with an existing ticket, or be split into smaller tasks by analyzing overlaps with current tickets.

Core Features & Use Cases

Analyze overlaps with tickets in .workaholic/tickets/todo and .workaholic/tickets/icebox to inform decisions.
Suggest merges when two tickets address the same goal and are overlapping, or recommend splits when a ticket is too broad.
Provide a structured decision with recommended next steps to maintain a clean, atomic ticket history.

Quick Start

Describe a new ticket in natural language and receive a structured recommendation with actions to take.

Frequently Asked Questions about discover-ticket

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

FAQPage Schema

How do I check if a new ticket overlaps with existing ones in my backlog?▼

To check ticket overlaps, analyze proposed tickets against current todo and icebox pools by evaluating key files, goals, and implementation scope to categorize matches and determine ticket viability.

When should I split or merge engineering tickets?▼

You should merge tickets when two address the same goal and overlap, or split tickets when a proposed task is too broad, ensuring a clean and atomic ticket history.

What is the best way to organize a backlog with duplicate tickets?▼

Organize backlogs by analyzing duplicate tickets for overlapping goals and implementation scope, then output a structured decision with explicit actions to merge, split, or create new tickets.

How do I analyze ticket viability before adding it to the icebox?▼

Analyze ticket viability by searching existing todo and icebox pools for overlaps, evaluating key files and implementation scope to output a structured decision with suggested next steps.

Can I get a structured recommendation on whether to proceed with a proposed ticket?▼

Yes, describe a new ticket in natural language to receive a structured recommendation with explicit actions and suggested next steps to maintain a clean, atomic ticket history.