# To Tickets (to-tickets)

> Breaks a plan, spec or conversation into tracer-bullet tickets with blocking edges and publishes them to the configured tracker.

- Category: [Task Breakdown](https://www.myskills.tools/en/categories/task-breakdown/)
- Source: Community · Matt Pocock
- Repository: https://github.com/mattpocock/skills/tree/main/skills/engineering/to-tickets (commit 9e2abf8)
- SKILL.md: https://github.com/mattpocock/skills/blob/main/skills/engineering/to-tickets/SKILL.md
- Install command: `npx skills add mattpocock/skills --skill to-tickets`
- License: MIT
- Compatible with: Claude Code, Codex, Copilot, Gemini CLI
- Permissions: read-repo ✓, write-files ✓, shell ✗, network ✓
- Status: Scan passed
- A rule scan cannot catch every risk. Read this skill's SKILL.md and check its permissions before installing.
- ⚠ With a real tracker it creates issues and applies the ready-for-agent label.

## Core rule

Each slice cuts a narrow but complete path through every layer (schema, API, UI, tests): vertical, not a horizontal slice of one layer.

## Execution Phases

1. **Gather context** — Work from the conversation; if given a spec path or issue number or URL, fetch and read its full body and comments.
2. **Explore the codebase** — Optionally explore the code, use the project's domain vocabulary, respect ADRs and look for prefactoring opportunities.
3. **Draft vertical slices** — Split into demoable tickets that fit one context window, each with blockers; sequence wide refactors as expand–contract.
4. **Quiz the user** — Show a numbered list with title, blockers and what each delivers, ask about granularity and edges, and iterate until approved.
5. **Publish tickets** — In dependency order, write one file per ticket under .scratch/ or create one issue each on the tracker with native blocking links; never modify the parent issue.

## Permissions (summarised from SKILL.md)

| Capability | Needed | Details |
|---|---|---|
| File writes | Limited | With a local tracker, writes only one file per ticket under .scratch/<feature-slug>/issues/. |
| Command execution | Not required | The instructions do not call for running commands. |
| Network outbound | Limited | Only the configured issue tracker (e.g. GitHub, Linear), to read referenced issues and create tickets. |

## SKILL.md frontmatter (YAML)

```yaml
---
name: to-tickets
description: 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).
disable-model-invocation: true
---
```

Home: https://www.myskills.tools/en/ · URL: https://www.myskills.tools/en/skills/to-tickets/