create-ticket

Creates lightweight tracker tickets with TL;DR summaries, classifications, and release groupings.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/bbenefield89/skills --skill create-ticket-bbenefield89
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-ticket
Source: https://github.com/bbenefield89/skills/tree/main/skills/create-ticket
Command: npx skills add https://github.com/bbenefield89/skills --skill create-ticket-bbenefield89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a new work item often means writing a vague ticket that lacks context, classification, or a clear place in the project backlog. This Skill creates a consistent, lightweight tracker ticket with a plain-language title, a short TL;DR, and the correct metadata so ideas enter the workflow properly from the start. ## Core Features & Use Cases - Structured Ticket Drafting: Writes a concrete, scannable title and a one- or two-sentence TL;DR body following the ASD-STE100 simplified writing standard. - Classification and Release Grouping: Applies configured ticket classifications, needs-details state, and release groupings, inferring the best fit and asking for confirmation when ambiguous. - Duplicate Detection and Positioning: Searches for existing equivalent tickets before creating a new one and places the ticket in the correct position within the project's TODO column. - Use Case: A developer has a new feature idea during a discussion. Use this Skill to draft the ticket, preview the title, body, classification, and backlog position, get approval, and create it in the tracker without writing a full specification. ## Quick Start Create a ticket for adding dark mode support to the settings page and place it near the top of the TODO column.

Frequently Asked Questions about create-ticket

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

FAQPage Schema
How do I create a project ticket with a TL;DR summary?

Describe the idea in conversation and the Skill drafts a concrete title plus a one- or two-sentence TL;DR body. It previews the full ticket including classification and position, then creates it only after your explicit approval.

How does the ticket creation skill handle duplicate tickets?

It searches the tracker for existing equivalent tickets before proposing a new one. If a plausible duplicate is found, it asks whether to reuse that ticket instead of creating a new one.

What happens if the tracker configuration is missing?

The Skill reads docs/agents/bb-skills.md as its configuration contract. If that file is absent, incomplete, or contradicts the tracker, it stops and directs you to run the setup-bb-skills skill first.

Does create-ticket also write specifications or subtasks?

No. It creates only the lightweight initial ticket with a TL;DR body. Specifications and child tasks are handled by separate downstream skills such as ticket-to-spec and spec-to-tasks.

What happens if ticket creation partially fails?

The Skill does not delete a partially created ticket. It reports which steps succeeded, such as creation or positioning, and what remains to be completed manually.