ticket-format

Solid

Canonical three-section structure for Linear and Superset tickets in this repo. Use when creating, drafting, or grooming a ticket.

Code & Development 14,079 stars 1259 forks Updated today NOASSERTION

Install

View on GitHub

Quality Score: 81/100

Stars 20%

100

Recency 20%

100

Frontmatter 20%

Documentation 15%

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# Ticket Format ## Context 2–4 sentences. What's broken or wanted, and why. Outcome-focused, not solution-focused. ## References Where the ticket came from. Omit section if none. | Source | Who | Link | Date | |--------|-----|------|------| | Slack #feedback | @alice | [thread](…) | 2026-05-10 | ## Implementation notes Agent-groomed. Leave empty if you don't have codebase context; a later grooming pass will fill it in. When you do fill it in, use these sub-headings and skip what doesn't apply: - `### Files`: `path:line` + why relevant - `### Approach`: one paragraph - `### Related code`: similar patterns in the repo - `### Gotchas`: constraints, prior incidents

Details

Author: superset-sh
Repository: superset-sh/superset
Created: 10 months ago
Last Updated: today
Language: TypeScript
License: NOASSERTION

Bundled in these plugins

superset

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

to-tickets

Use when breaking a plan into tracer-bullet GitHub issues with blocking edges.

6 Updated 5 days ago

Kripu77

API & Backend Listed

to-tickets

Slice a spec, plan or conversation into vertical tracer-bullet tickets on Linear, each carrying its blocking edges as native relations.

0 Updated 2 weeks ago

jacobrees-canoncore

Data & Documents Listed

single-ticket

Retrofit an existing ticket to the five-section leaf-ticket standard so it can be handled by :plan --ticket-driven or a fleet run. Interviews toward the missing structure with /slopstop:grill, drafts the five sections, runs the huge-tier adversary loop, then confirms and pushes — preserving the original ticket verbatim below a separator. Interactive only. Invoke as /slopstop:single-ticket <TICKET-ID>.

2 Updated 3 days ago

iansmith