ticket-format

Solid

Use when creating, drafting, or grooming a Linear or Superset ticket in this repo. Defines the canonical three-section structure.

Code & Development 12,636 stars 1130 forks Updated today NOASSERTION

Install

View on GitHub

Quality Score: 81/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
34
Issue Health 10%
50
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
9 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

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>.

0 Updated today
iansmith
Code & Development Listed

to-tickets

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

1 Updated today
taewanu
AI & Automation Solid

plan-to-tickets

Use when a large plan, PRD, feature, refactor, research plan, or multi-step coding task must be split into small ready-for-agent tickets with acceptance criteria, verification commands, blockers, and vertical tracer-bullet slices. Do not use for small tasks that should be implemented directly, single-bug fixes, or chat-only summaries.

138 Updated yesterday
AnastasiyaW