skills.rest
Suge8
Suge8COMMUNITY
Explore all skills by this author →
WebsiteGitHub

to-tickets

Converts aligned discussions into spec headers and tracer-bullet tickets for issue trackers.

Updated Sep 14, 2026
Search Tags:#spec writing#issue tracker#github issues#workflow planning#vertical slice#ticket generation#tracer bullet
One-click install
npx skills add https://github.com/Suge8/skills --skill to-tickets-suge8
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/Suge8/skills/tree/main/workflow/to-tickets
Command: npx skills add https://github.com/Suge8/skills --skill to-tickets-suge8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a long design discussion into actionable work items is error-prone: specs drift from what was agreed, tickets overlap, and dependencies get lost. This Skill synthesizes an already-aligned conversation into a single spec header plus a set of vertical-slice tickets with explicit blocking edges, confirmed once and published once. ## Core Features & Use Cases - Spec Header Drafting: Produces a structured spec covering problem statement, solution, implementation decisions, test decisions, and out-of-scope items, grounded in codebase terminology from CONTEXT.md and ADRs. - Vertical-Slice Ticket Generation: Creates tracer-bullet tickets that cut through every layer (schema, API, UI, tests), each independently demonstrable with executable acceptance criteria, plus spine tickets for shared files and expand-contract ordering for wide refactors. - One-Shot Publishing: Publishes to local files under .scratch/<feature-slug>/ or to real trackers like GitHub/GitLab as parent spec issues with blocked sub-issues and triage labels. - Use Case: After a design session about adding a notifications feature, invoke this Skill to produce a spec.md and five numbered, dependency-ordered tickets ready for agent implementation. ## Quick Start Ask the agent to turn the current aligned discussion into a spec header and tracer-bullet tickets using the to-tickets workflow.

Frequently Asked Questions about to-tickets

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

FAQPage Schema
How do I turn a design discussion into actionable tickets?▼

Run the to-tickets workflow after the discussion is aligned. It drafts a spec header and vertical-slice tickets with blocking edges, shows them once for your confirmation, then publishes them to your configured tracker in a single pass.

What is a tracer-bullet or vertical-slice ticket?▼

A vertical-slice ticket cuts through every layer—schema, API, UI, and tests—forming one narrow complete path that can be independently demonstrated. Each acceptance criterion maps to an executable check at a public seam defined during planning.

Can I publish tickets to GitHub or GitLab issues?▼

Yes. The spec header becomes a parent issue with a spec label, and tickets become child issues using native blocking relations when supported, otherwise blocking references are written into the body. Local file output under .scratch/ is also supported.

How are large-scale refactors handled in ticket planning?▼

Wide refactors use expand-contract ordering instead of vertical slices: add the new form alongside the old, migrate call sites in per-package batches as separate blocked tickets, then remove the old form last. This keeps CI green between batches.

What happens if no ticket tracker is configured?▼

The Skill expects a ticket store and label vocabulary to already exist. If none is configured, it tells you to run /setup-tracker first rather than guessing a destination for the published tickets.

Related Skills

Explore More Software Engineering Skills→
guhans6guhans6

grill-with-docs

Validate project plans against a domain model and update CONTEXT.md and ADRs.

Community
Advanced
MaxWolf-01MaxWolf-01
3

to-tickets

Breaks a grilled specification into dependency-ordered tracer-bullet ticket files with blocking edges.

Community
Advanced
pattobrienpattobrien
2

to-tickets

Breaks plans and specs into tracer-bullet tickets with declared blocking edges.

Community
Intermediate
liangmiQwQliangmiQwQ

doc-style

Apply documentation guidelines to write concise prose for API docs, manuals, and knowledge bases.

Community
Basic