---
title: "Specification to Dependency-Aware Tickets: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/skills/mattpocock-to-tickets/
description: "Splits an agreed plan into small vertical slices, with explicit blocking relationships and a review before publication."
---

# Specification to Dependency-Aware Tickets: review, setup & limitations · Undominated.ai

> Splits an agreed plan into small vertical slices, with explicit blocking relationships and a review before publication.

[← Explore all skills](/skills/)

PLANNING AND DELIVERY / Matt Pocock

# Specification to Dependency-Aware Tickets

Splits an agreed plan into small vertical slices, with explicit blocking relationships and a review before publication.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/engineering/to-tickets/SKILL.md)

SOURCE REVIEW

 Reviewed 2026-10-15
 Evidence 16 linked sources
 Publisher Matt Pocock
 Licence [MIT ↗](https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/LICENSE)
 Revision 49dd158d1076
 [Read what was—and wasn’t—checked ↓](#review)

“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).”

 [Matt Pocock · upstream description ↗](https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/engineering/to-tickets/SKILL.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Asks for user agreement on the proposed breakdown before creating the tickets.
- Keeps each slice testable across the system and records dependency edges, including expand-and-contract sequencing for broad changes.

### A good fit for

 - Preparing implementation work that several contributors can pick up in dependency order
- Turning an approved specification into separate local Markdown, GitHub or GitLab issues
- Sequencing a wide rename or retype as expand, batched migrate and contract tickets
- Plan a shared integration branch and final verification ticket when migration batches cannot pass independently.

### Weigh up before choosing

 - Ticket publication is not transactional: partial failures or repeated runs can leave duplicates and incomplete dependency links.
- When the source is an existing issue, 49dd158d makes each ticket its sub-issue through the tracker doc, which on GitHub is gh issue create --parent or gh issue edit <parent> --add-sub-issue. The same file says not to close or modify any parent issue. Decide whether that association is permitted; use textual references if parent mutation is out of scope.
- Native blocking links depend on tracker capabilities and account entitlements; the companion supplies textual fallbacks.
- The download carries SKILL.md and agents/openai.yaml. The skill expects the tracker that setup-matt-pocock-skills configures. Without that configuration it tells the user to run setup-matt-pocock-skills, which is not in the download.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - skills/engineering/to-tickets/SKILL.md
- README.md (installation and setup sections; the README has no licence section)
- LICENSE (MIT, copyright 2026 Matt Pocock)
- skills/engineering/to-tickets/agents/openai.yaml
- skills/engineering/setup-matt-pocock-skills/SKILL.md
- skills/engineering/setup-matt-pocock-skills/agents/openai.yaml
- skills/engineering/setup-matt-pocock-skills/domain.md
- skills/engineering/setup-matt-pocock-skills/issue-tracker-github.md
- skills/engineering/setup-matt-pocock-skills/issue-tracker-gitlab.md
- skills/engineering/setup-matt-pocock-skills/issue-tracker-local.md
- skills/engineering/setup-matt-pocock-skills/triage-labels.md

### Our findings

 - The definition separates proposing the decomposition from publishing it.
- Its local tracker template writes one file per ticket, rather than a single combined task list; remote templates describe native links and fallbacks.
- Wide refactors are sequenced as expand–contract: add the new form, migrate call sites in batches sized by blast radius, each blocked by the expand, then delete the old form in a ticket blocked by every batch.
- A reference passed as an argument (spec path, issue number or URL) is fetched and read with its full body and comments, and each slice must fit in a single fresh context window.
- Re-pinned from c55ee46073ed923f86ce59a5eb3b6d895095d1b7 to 49dd158d1076134a641b33efb035946536778336: to-tickets/SKILL.md now makes each ticket a sub-issue when the source was an existing issue, and drops the Blocked by section when blockers were set as native edges. issue-tracker-github.md gained the sub-issue commands (gh 2.94+, or the sub_issues API on older gh). At this revision the setup companion also creates any configured triage label the GitHub or GitLab tracker lacks (gh label create / glab label create), when the triage skill is installed.

### Not established by this review

 - No upstream definition, helper, installer or generated workload was executed.
- No end-to-end agent session or effectiveness benchmark was run.
- Not executed: it was not installed or run.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Add a skill to your workflow.

[Upstream setup instructions ↗](https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/README.md)

DOCUMENTED COMMAND

 npx skills add mattpocock/skills --skill to-tickets --skill setup-matt-pocock-skills Copy command ↗

Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.

 Optional: install the reviewed revision

Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose.

 npx skills add https://github.com/mattpocock/skills/tree/49dd158d1076134a641b33efb035946536778336 --skill to-tickets --skill setup-matt-pocock-skills Copy reviewed-revision command ↗ - Install the complete skill directory, including its references and helpers; select your AI tools and project or global scope.
- Run the setup companion once. Inspect its proposed edits to AGENTS.md or CLAUDE.md and docs/agents/ before accepting; it configures GitHub, GitLab or local Markdown tracking. At this revision the setup companion also creates any configured triage label the GitHub or GitLab tracker lacks (gh label create / glab label create), when the triage skill is installed.
- Review the instructions before invoking them. The source revision shown here is the one reviewed; the installer was not executed or version-pinned by this review.
- For manual installation instead, download the complete bundle from https://undominated.ai/resources/skills/mattpocock-to-tickets/bundle.zip and extract it into a new directory. It holds SKILL.md and agents/openai.yaml unchanged at revision 49dd158d, the upstream licence and an attribution file.
- Place the extracted directory in your host's documented skills directory, named to-tickets. Keep SKILL.md and the licence together.

### Before you start

 - Node.js/npm and git for the documented Skills installer
- An agent host that supports the skill format and the tools required by the workflow
- Configured tracker access: authenticated gh or glab for remote issues, or a writable local Markdown directory

### Compatibility

Claude Code · Codex · GitHub Copilot · Gemini CLI

### Repository instructions and host-provided tools

 - Read the specification and relevant source/context
- Create ticket files or authenticated tracker issues after agreement
- Write dependency links and permitted labels or associations

### Cost model

MIT-licensed instructions; agent and tracker account costs remain separate.

THE COMPLETE REVIEWED DEFINITION

## Read it before you reuse it.

Original source bytes, with attribution. Review the host-specific setup notes above.

 Copy definition ↗ [Download complete resource + licence ↗](/resources/skills/mattpocock-to-tickets/bundle.zip)[Raw Markdown ↗](/resources/skills/mattpocock-to-tickets/definition.md)
 ---
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
---

# To Tickets

Break a plan, spec, or conversation into a set of **tickets**: tracer-bullet vertical slices, each declaring the tickets that **block** it.

The issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run `/setup-matt-pocock-skills`.

## Process

### 1. Gather context

Work from whatever is already in the conversation context. If the user passes a reference (a spec path, an issue number or URL) as an argument, fetch it and read its full body and comments.

### 2. Explore the codebase (optional)

If you have not already explored the codebase, do so to understand the current state of the code. Ticket titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.

Look for opportunities to prefactor the code to make the implementation easier. "Make the change easy, then make the easy change."

### 3. Draft vertical slices

Break the work into **tracer bullet** tickets.

<vertical-slice-rules>

- Each slice cuts a narrow but COMPLETE path through every layer (schema, API, UI, tests): vertical, NOT a horizontal slice of one layer
- A completed slice is demoable or verifiable on its own
- Each slice is sized to fit in a single fresh context window
- Any prefactoring should be done first

</vertical-slice-rules>

Give each ticket its **blocking edges**: the other tickets that must complete before it can start. A ticket with no blockers can start immediately.

**Wide refactors are the exception to vertical slicing.** A **wide refactor** is one mechanical change (rename a column, retype a shared symbol) whose **blast radius** fans across the whole codebase, so a single edit breaks thousands of call sites at once and no vertical slice can land green. Don't force it into a tracer bullet; sequence it as **expand–contract**. First expand: add the new form beside the old so nothing breaks. Then migrate the call sites over in batches sized by blast radius (per package, per directory), each batch its own ticket blocked by the expand, keeping CI green batch to batch because the old form still exists. Finally contract: delete the old form once no caller remains, in a ticket blocked by every migrate batch. When even the batches can't stay green alone, keep the sequence but let them share an integration branch that all block a final integrate-and-verify ticket; green is promised only there.

### 4. Quiz the user

Present the proposed breakdown as a numbered list. For each ticket, show:

- **Title**: short descriptive name
- **Blocked by**: which other tickets (if any) must complete first
- **What it delivers**: the end-to-end behaviour this ticket makes work

Ask the user:

- Does the granularity feel right? (too coarse / too fine)
- Are the blocking edges correct: does each ticket only depend on tickets that genuinely gate it?
- Should any tickets be merged or split further?

Iterate until the user approves the breakdown.

### 5. Publish the tickets to the configured tracker

Publish the approved tickets. **How** depends on the tracker `/setup-matt-pocock-skills` configured; the tickets are the same either way, only the shape of the blocking edges changes:

- **Local files** → write one file per ticket under `.scratch/<feature-slug>/issues/<NN>-<slug>.md`, numbered from `01` in dependency order (blockers first). Each file's "Blocked by" lists the numbers/titles it depends on. Use the per-ticket file template below: one ticket per file, never a single combined file.
- **A real issue tracker (GitHub, Linear, …)** → publish one issue per ticket in dependency order (blockers first) so each ticket's blocking edges can reference real identifiers. Use the platform's native blocking relationship where it has one; otherwise set each ticket's "Blocked by" to the blocking issues. If the source was an existing issue, make each ticket its sub-issue (tracker doc's operation). Apply the `ready-for-agent` triage label unless instructed otherwise; the tickets are agent-grabbable by construction.

Work the **frontier**: any ticket whose blockers are all done. For a purely linear chain that means top to bottom.

Do NOT close or modify any parent issue.

<local-ticket-template>

# <NN>: <Ticket title>

**What to build:** the end-to-end behaviour this ticket makes work, from the user's perspective, not a layer-by-layer implementation list.

**Blocked by:** the numbers/titles of the tickets that gate this one, or "None (can start immediately)".

**Status:** ready-for-agent

- [ ] Acceptance criterion 1
- [ ] Acceptance criterion 2

</local-ticket-template>

<issue-template>

## Parent

A reference to the parent issue on the tracker (if the source was an existing issue, otherwise omit this section).

## What to build

The end-to-end behaviour this ticket makes work, from the user's perspective, not layer-by-layer implementation.

## Acceptance criteria

- [ ] Criterion 1
- [ ] Criterion 2

## Blocked by

- A reference to each blocking ticket, or "None (can start immediately)". Omit this section when blockers were set as native edges.

</issue-template>

In either form, avoid specific file paths or code snippets: they go stale fast. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it and note briefly that it came from a prototype. Trim to the decision-rich parts, not a working demo, just the important bits.

The download contains SKILL.md . Extract the whole bundle; the supporting files are required. Inspect the included MANIFEST.json for file hashes.

By **Matt Pocock**. [Exact upstream source ↗](https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/engineering/to-tickets/SKILL.md) · [Licence](/resources/skills/mattpocock-to-tickets/LICENSE.txt) · [Attribution](/resources/skills/mattpocock-to-tickets/ATTRIBUTION.txt)

SHA-256 56ec23c5b2782785d4e65bff9e315b6d3aeb4ef977c174a219e99489fada1995

 Read the applicable licence MIT License

Copyright (c) 2026 Matt Pocock

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Definition at the reviewed revision ↗](https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/engineering/to-tickets/SKILL.md) Checked 2026-10-13 https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/engineering/to-tickets/SKILL.md Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, access
- [Publisher installation and compatibility guidance ↗](https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/README.md) Checked 2026-10-13 https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/README.md Supports: install, compatibility
- [Licence at the reviewed revision ↗](https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/LICENSE) Checked 2026-10-13 https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/LICENSE Supports: license, access.cost
- [Reviewed companion: skills/engineering/to-tickets/agents/openai.yaml ↗](https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/engineering/to-tickets/agents/openai.yaml) Checked 2026-10-13 https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/engineering/to-tickets/agents/openai.yaml Supports: review
- [Skills installer: README.md ↗](https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/README.md) Checked 2026-10-13 https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/README.md Supports: install
- [Skills installer: src/git.ts ↗](https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/src/git.ts) Checked 2026-10-13 https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/src/git.ts Supports: install
- [Skills installer: src/source-parser.ts ↗](https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/src/source-parser.ts) Checked 2026-10-13 https://github.com/vercel-labs/skills/blob/7407f3893ad4dceab546ac002c3ef806e4000c73/src/source-parser.ts Supports: install
- [Reviewed companion: skills/engineering/setup-matt-pocock-skills/SKILL.md ↗](https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/engineering/setup-matt-pocock-skills/SKILL.md) Checked 2026-10-13 https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/engineering/setup-matt-pocock-skills/SKILL.md Supports: review, limitations, install, access
- [Reviewed companion: skills/engineering/setup-matt-pocock-skills/agents/openai.yaml ↗](https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/engineering/setup-matt-pocock-skills/agents/openai.yaml) Checked 2026-10-13 https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/engineering/setup-matt-pocock-skills/agents/openai.yaml Supports: review
- [Reviewed companion: skills/engineering/setup-matt-pocock-skills/domain.md ↗](https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/engineering/setup-matt-pocock-skills/domain.md) Checked 2026-10-13 https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/engineering/setup-matt-pocock-skills/domain.md Supports: review, limitations, install, access
- [Reviewed companion: skills/engineering/setup-matt-pocock-skills/issue-tracker-github.md ↗](https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/engineering/setup-matt-pocock-skills/issue-tracker-github.md) Checked 2026-10-13 https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/engineering/setup-matt-pocock-skills/issue-tracker-github.md Supports: review, limitations, install, access
- [Reviewed companion: skills/engineering/setup-matt-pocock-skills/issue-tracker-gitlab.md ↗](https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/engineering/setup-matt-pocock-skills/issue-tracker-gitlab.md) Checked 2026-10-13 https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/engineering/setup-matt-pocock-skills/issue-tracker-gitlab.md Supports: review, limitations, install, access
- [Reviewed companion: skills/engineering/setup-matt-pocock-skills/issue-tracker-local.md ↗](https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/engineering/setup-matt-pocock-skills/issue-tracker-local.md) Checked 2026-10-13 https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/engineering/setup-matt-pocock-skills/issue-tracker-local.md Supports: review, limitations, install, access
- [Reviewed companion: skills/engineering/setup-matt-pocock-skills/triage-labels.md ↗](https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/engineering/setup-matt-pocock-skills/triage-labels.md) Checked 2026-10-13 https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/engineering/setup-matt-pocock-skills/triage-labels.md Supports: review, limitations, install, access
- [Pinned definition rechecked for the 2026-10-15 resource wave ↗](https://raw.githubusercontent.com/mattpocock/skills/49dd158d1076134a641b33efb035946536778336/skills/engineering/to-tickets/SKILL.md) Checked 2026-10-15 https://raw.githubusercontent.com/mattpocock/skills/49dd158d1076134a641b33efb035946536778336/skills/engineering/to-tickets/SKILL.md Supports: bestFor, review
- [Pinned publisher installation text rechecked for the 2026-10-15 resource wave ↗](https://raw.githubusercontent.com/mattpocock/skills/49dd158d1076134a641b33efb035946536778336/README.md) Checked 2026-10-15 https://raw.githubusercontent.com/mattpocock/skills/49dd158d1076134a641b33efb035946536778336/README.md Supports: limitations

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Conversation to Specification ↗ Turns an already-discussed change into a repository-aware specification for the configured issue tracker.](/skills/mattpocock-to-spec/)[### Conventional Branch ↗ Creates and validates Git branches against the Conventional Branch specification — feature/, bugfix/, hotfix/, release/, chore/ — with a validation ruleset, an invalid-example table, trunk detection and a mapping to Conventional Commits.](/skills/github-conventional-branch/)[### GitHub Release Workflow ↗ Cuts a library release end to end: tag-derived versioning, code-diff-first SemVer analysis against commit intent, Keep a Changelog authoring, and a gated release-branch plus PR handoff.](/skills/github-github-release/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Choose a toolkit](/tools/)
- [Inspect execution hosts](/agents/)
- [Check tool access](/mcp-servers/)
- [Check project dependencies](/check-repo/)
