Agent skill

To Tickets

by devcxl in devcxl/mattpocock-skills-zh

将计划、规范或当前对话拆分为一组 tracer-bullet ticket,每个 ticket 声明其阻塞边(blocking edges),发布到已配置的跟踪器——本地文件中每个 ticket 一个文件以文本表示边,真实跟踪器上以原生阻塞链接表示。

MITAuto-check passedDevelopment

Install To Tickets

skills CLI
$ npx skills add devcxl/mattpocock-skills-zh --skill to-tickets -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install devcxl/mattpocock-skills-zh to-tickets --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/devcxl/mattpocock-skills-zh.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/engineering/to-tickets .claude/skills/to-tickets && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
to-tickets
GitHub stars
437
Token cost
~693 tokens
SKILL.md length
184 words
Files
2
Skills in repo
19
Repo updated
First seen
Licence
MIT

At a glance

将计划、规范或当前对话拆分为一组 tracer-bullet ticket,每个 ticket 声明其阻塞边(blocking edges),发布到已配置的跟踪器——本地文件中每个 ticket 一个文件以文本表示边,真实跟踪器上以原生阻塞链接表示。

  • Works in 5 steps: 收集上下文 → 探索代码库(可选) → 起草垂直切片 → …
  • Development work in your project
  • SKILL.md covers 流程, Parent, What to build and Acceptance criteria, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

To Tickets is an agent skill from devcxl/mattpocock-skills-zh. 将计划、规范或当前对话拆分为一组 tracer-bullet ticket,每个 ticket 声明其阻塞边(blocking edges),发布到已配置的跟踪器——本地文件中每个 ticket 一个文件以文本表示边,真实跟踪器上以原生阻塞链接表示。

Its SKILL.md is about 690 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development. The repository describes itself as: Matt Pocock 技能集的中文翻译版 — 地道中文,原汁原味的技术术语。基于 mattpocock/skills 复刻。每日中午12点钟同步. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/to-tickets”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. 收集上下文
  2. 探索代码库(可选)
  3. 起草垂直切片
  4. 征求用户意见
  5. 将 ticket 发布到已配置的跟踪器

What it can do on your machine

Read from SKILL.md and the folder at commit 15ac33e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

To Tickets loads about 693 tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 184 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~34
When it runs · the whole SKILL.md, loaded when a task matches
~693

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from devcxl/mattpocock-skills-zh at commit 15ac33e, republished under its MIT licence (© devcxl). 184 words, ~693 tokens.

Download SKILL.mdSave it as .claude/skills/to-tickets/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
to-tickets
description
将计划、规范或当前对话拆分为一组 tracer-bullet ticket,每个 ticket 声明其阻塞边(blocking edges),发布到已配置的跟踪器——本地文件中每个 ticket 一个文件以文本表示边,真实跟踪器上以原生阻塞链接表示。
disable-model-invocation
true

拆分为 Ticket

将计划、规范或对话拆分为一组 ticket——tracer-bullet 垂直切片,每个都声明阻塞它的其他 ticket。

Issue 跟踪器和分类标签词汇表应已提供给你——如果没有,请告诉用户运行 /setup-matt-pocock-skills。

流程

1. 收集上下文

从对话上下文中已有的内容开始。如果用户传入引用(规范路径、Issue 编号或 URL)作为参数,获取它并读取其完整正文和评论。

2. 探索代码库(可选)

如果你尚未探索代码库,请先了解代码的当前状态。Ticket 标题和描述应使用项目的领域术语表词汇,并尊重你正在接触的区域的 ADR。

寻找预重构代码的机会,使实现更简单。"让改动变得容易,然后再做容易的改动。"

3. 起草垂直切片

将工作拆分为 tracer bullet ticket。

<vertical-slice-rules>
  • 每个切片在每个层面(schema、API、UI、测试)走一条狭窄但完整的通路——是垂直的,而不是某一层的水平切片
  • 一个完成的切片本身是可演示或可验证的
  • 每个切片大小适合单个全新的上下文窗口
  • 任何预重构应首先完成
</vertical-slice-rules>

为每个 ticket 指定其阻塞边——必须先完成才能开始的其他 ticket。没有阻塞项的 ticket 可以立即开始。

大范围重构是垂直切片的例外。 大范围重构 是一种机械性变更(重命名列、更改共享符号类型),其影响范围波及整个代码库,一次编辑会同时破坏数千个调用点,导致没有任何垂直切片能保持绿色。不要硬塞进 tracer bullet;按 扩展-收缩(expand–contract) 序列化。首先扩展:在旧形式旁边添加新形式,确保任何东西都没坏。然后按影响范围大小分批迁移调用点(按包、按目录),每批一个 ticket 被扩展阻塞,由于旧形式仍存在,CI 在批次之间保持绿色。最后收缩:所有调用者迁移完后删除旧形式,作为一个被每个迁移批次阻塞的 ticket。当批次本身也无法单独保持绿色时,保留这个序列,但让它们共享一个集成分支,所有批次都阻塞一个最终的"集成并验证" ticket——绿色只在那里承诺。

4. 征求用户意见

以编号列表的形式展示提议的拆解方案。对每个 ticket,展示:

  • 标题:简短描述性名称
  • 被以下阻塞:哪些其他 ticket(如果有)必须先完成
  • 交付内容:此 ticket 让哪个端到端行为生效

询问用户:

  • 粒度是否合适?(太粗 / 太细)
  • 阻塞边是否正确:每个 ticket 是否只依赖真正制约它的 ticket?
  • 是否需要合并或进一步拆分某些 ticket?

迭代直到用户批准拆解方案。

5. 将 ticket 发布到已配置的跟踪器

发布已批准的 ticket。发布方式取决于 /setup-matt-pocock-skills 配置的跟踪器——ticket 本身相同,只有阻塞边的形式不同:

  • 本地文件 → 在 .scratch/<feature-slug>/issues/<NN>-<slug>.md 下为每个 ticket 写入一个文件,按依赖顺序从 01 开始编号(阻塞项优先)。每个文件的 "Blocked by" 列出它依赖的编号/标题。使用下面的 per-ticket 文件模板:一个 ticket 一个文件,绝不合并为一个文件。
  • 真实 issue 跟踪器(GitHub、Linear……) → 按依赖顺序每个 ticket 发布一个 issue(阻塞项优先),这样每个 ticket 的阻塞边可以引用真实标识符。平台支持原生阻塞关系时就使用;否则把每个 ticket 的 "Blocked by" 设为阻塞它的 issue。如果来源是一个已有 issue,则把每张 ticket 设为它的子 issue(使用 tracker 文档中的操作)。除非另有指示,应用 ready-for-agent triage 标签——这些 ticket 本身就具备 agent 可领取性。

按前沿推进:任意一个阻塞项已全部完成的 ticket。对纯粹的线性链来说就是从上到下。

不要关闭或修改任何父 issue。

<local-ticket-template>

<NN>: <Ticket 标题>

What to build: 此 ticket 让哪个端到端行为生效——从用户视角出发,而不是逐层的实现清单。

Blocked by: 制约此 ticket 的其他 ticket 的编号/标题,或 "None (can start immediately)"。

Status: ready-for-agent

  • 验收标准 1
  • 验收标准 2
</local-ticket-template>
<issue-template>

Parent

跟踪器上父 issue 的引用(若源为已有 issue,否则省略本节)。

What to build

此 ticket 让哪个端到端行为生效——从用户视角出发,而不是逐层实现。

Acceptance criteria

  • 标准 1
  • 标准 2

Blocked by

  • 每个阻塞 ticket 的引用,或 "None (can start immediately)"。若阻塞关系已通过原生边设置,则省略本节。
</issue-template>

无论哪种形式,避免具体的文件路径或代码片段——它们很快就会过时。例外情况:如果原型产出的代码片段比文字更精确地编码了某个决策(状态机、reducer、schema、类型结构),将其内联并简要说明来自原型。精简到决策密集的部分——不是可工作的演示,只是重要的那些。

© devcxl, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/engineering/to-tickets of devcxl/mattpocock-skills-zh.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 15ac33e

Compare with similar skills

To Tickets next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

To Tickets compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
To Tickets this skilldevcxl/mattpocock-skills-zh437—~693Automated safety check: PassMIT
Vercel Composition Patternssupabase/supabase111k59 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 59 repos~726 tokens
    DevelopmentAuto-check passed
  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from devcxl/mattpocock-skills-zh

All 19 skills in this repo
  • Git Guardrails Claude Code

    devcxl/mattpocock-skills-zh

    设置 Claude Code 钩子,在危险 Git 命令(push、reset --hard、clean、branch -D 等)执行前将其拦截。当用户想要防止破坏性 Git 操作、添加 Git 安全钩子或在 Claude Code 中阻止 git push/reset 时使用。

    437 GitHub starsUsed in 1 repo~420 tokens
    Auto-check passed
  • Triage

    devcxl/mattpocock-skills-zh

    将 issue 和外部 PR 推过一组分诊角色的状态机——分类、验证、必要时盘问,并写出 agent 就绪的任务简报. An agent skill from devcxl/mattpocock-skills-zh.

    437 GitHub starsUsed in 1 repo~816 tokens
    Auto-check passed
  • Codebase Design

    devcxl/mattpocock-skills-zh

    设计深度模块的共享词汇。当用户想要设计或改进模块的接口、寻找深化机会、决定 seam 的位置、让代码更可测试或更易被 AI 导航,或者其他 skill 需要深度模块词汇时使用。

    437 GitHub stars~809 tokensUpdated yesterday
    Auto-check passed
  • Diagnosing Bugs

    devcxl/mattpocock-skills-zh

    针对棘手 bug 和性能回归的诊断循环。当用户说"诊断"/"调试这个",或报告某处崩溃/报错/不正常/缓慢时使用. An agent skill from devcxl/mattpocock-skills-zh.

    437 GitHub stars~973 tokensUpdated yesterday
    Auto-check passed
  • Domain Modeling

    devcxl/mattpocock-skills-zh

    构建和完善项目的领域模型。当讨论代码库术语、编写或编辑 GLOSSARY.md,或记录或编辑 ADR 时使用. An agent skill from devcxl/mattpocock-skills-zh.

    437 GitHub stars~412 tokensUpdated yesterday
    Auto-check passed
  • Migrate To Shoehorn

    devcxl/mattpocock-skills-zh

    将测试文件从 as 类型断言迁移到 @total-typescript/shoehorn。当用户提到 shoehorn、想要在测试中替换 as、或需要部分测试数据时使用。

    437 GitHub stars~522 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about To Tickets

What does To Tickets do?

将计划、规范或当前对话拆分为一组 tracer-bullet ticket,每个 ticket 声明其阻塞边(blocking edges),发布到已配置的跟踪器——本地文件中每个 ticket 一个文件以文本表示边,真实跟踪器上以原生阻塞链接表示。. To Tickets is an agent skill from devcxl/mattpocock-skills-zh.

When should I use To Tickets?

To Tickets fits situations like: development work in your project.

How do I install To Tickets in Claude Code?

Run `npx skills add devcxl/mattpocock-skills-zh --skill to-tickets -a claude-code`. Or copy the skill folder (skills/engineering/to-tickets in devcxl/mattpocock-skills-zh) into .claude/skills/to-tickets in your project. Claude Code loads it when a task matches its description.

How do I install To Tickets in Codex?

Run `npx skills add devcxl/mattpocock-skills-zh --skill to-tickets -a codex`. Or copy the skill folder (skills/engineering/to-tickets in devcxl/mattpocock-skills-zh) into .agents/skills/to-tickets in your project. Codex loads it when a task matches its description.

Can I use To Tickets in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add devcxl/mattpocock-skills-zh --skill to-tickets -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/to-tickets, .gemini/skills/to-tickets, .github/skills/to-tickets and .opencode/skills/to-tickets in your project.

What does To Tickets need to run?

SKILL.md names no scripts, command-line tools or credentials: To Tickets is instructions for the agent only.

Does To Tickets access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is To Tickets safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does To Tickets use?

To Tickets is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does To Tickets use?

About 693 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to To Tickets?

Skills that share tags, products or a category with To Tickets: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains To Tickets?

devcxl (a GitHub user) maintains it in devcxl/mattpocock-skills-zh, which has 437 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 7, 2026.

Source: devcxl/mattpocock-skills-zh on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.