create-tickets
Installation
SKILL.md
Tickets Creator
Goal: decompose a product/engineering document into a high-level, product-oriented list of tickets, prioritized and dependency-aware, that can be created verbatim in an external tracker (Linear, GitHub Issues, Jira).
The output of this skill is intended to leave the repo. Tickets describe what to ship in product terms, not how to engineer it.
When to use this vs /create-implementation-plan
Both skills break work down, but they answer different questions for different audiences.
| Aspect | /create-tickets |
/create-implementation-plan |
|---|---|---|
| Question | What shippable units of work make up this thing? | How will we build this one thing, step by step? |
| Audience | Product + engineering | Engineering |
| Granularity | High-level, product-oriented, backlog-sized | Granular, task-by-task, file-aware |
| Scope | The whole feature, decomposed | A single ticket, planned |
| Destination | External tracker (Linear, GitHub Issues, Jira) | Stays in .specs/ |
| Sequence | Priority + declared dependencies | Phases, vertical slices, tracer bullet |