skills.rest
EarlBear
EarlBearOFFICIAL
Explore all skills by this author →
GitHub

handling-jira-stubs

Classify underspecified Jira tickets into Active, Deferred, or Retired states.

Updated Apr 13, 2026
Search Tags:#automation#workflow#scoping#jira#grooming#epic-management#stub-ticket
One-click install
npx skills add https://github.com/EarlBear/homebrew-tap --skill handling-jira-stubs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handling-jira-stubs
Source: https://github.com/EarlBear/homebrew-tap/tree/main/plugins-bundle/jira-manager/skills/handling-jira-stubs
Command: npx skills add https://github.com/EarlBear/homebrew-tap --skill handling-jira-stubs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Jira projects often accumulate under-specified tickets ("stubs") that block progress because they lack enough context to scope or implement. This skill classifies and routes such stubs to the correct lifecycle, enabling timely grooming, re-parenting, and decisioning.

Core Features & Use Cases

  • Classify stubs by evaluating description length, presence of attachments, ticket type, and parent epic to decide between Active, Deferred, or Retired states.
  • Re-parent stubs under a dedicated 🦴 Stubs Epic when scoping or deferring, keeping the backlog organized and isolated from active work.
  • Provide a structured scoping workflow with templates to capture goals, acceptance criteria, and next steps, ensuring consistency across tickets.

Quick Start

Provide the stub ticket details and the target project context to start the classification workflow.

Frequently Asked Questions about handling-jira-stubs

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

FAQPage Schema
How do I identify and groom under-specified Jira tickets in my backlog?▼

You classify stubs by analyzing description length, attachments, type, and parent epic to route under-specified Jira tickets into Active, Deferred, or Retired states, ensuring traceable backlog hygiene.

What is a Jira stub ticket and when should it be retired or deferred?▼

A Jira stub ticket is an under-specified issue lacking context to scope or implement. It should be retired or deferred when classification based on its description and attachments determines it is not ready for active work.

How do I batch classify Jira stub tickets for an entire project?▼

You batch classify Jira stub tickets by running a campaign across a target project, applying deterministic detection rules to evaluate each ticket and guide the lifecycle management workflow for the entire backlog.

Can I re-parent stub tickets under a dedicated Epic in Jira?▼

Yes, you can re-parent stub tickets under a dedicated Stubs Epic when scoping or deferring. This isolates under-specified issues from active work to keep the backlog organized and clean.

Do I need a specific Jira setup to start a stub ticket scoping workflow?▼

You need to provide stub ticket details and the target project context to start the classification workflow. The process applies deterministic detection and lifecycle management without requiring external dependencies.

Related Skills

Explore More Product & Management Skills→
drdatarulzdrdatarulz
3

implement-ticket

Implement a single ticket end-to-end with TI standards and Git commits.

Community
Advanced
lciaccilciacci

ticket-craft

Create self-contained software tickets with acceptance criteria and verification commands.

Community
Advanced
webdevtodayjasonwebdevtodayjason
7

bmad-prd

Generate structured PRDs, architecture documents, epics, and user stories.

Community
Advanced
phrazzldphrazzld
13

groom

Orchestrate interactive and automated backlog grooming with the GitHub API.

Community
Advanced