to-issues
vinvcn/mattpocock-skills-zh-cn
Break plans into vertical-slice issues for your issue tracker using tracer-bullet methodology.
What is to-issues?
Converts plans, specs, or PRDs into granular, independently-assignable issues using vertical slices (tracer bullets). Each slice is a thin end-to-end path through all integration layers. Use this when you need to decompose work into actionable tickets for your team's issue tracker.
- Decomposes plans into tracer-bullet vertical slices rather than horizontal layers
- Classifies slices as HITL (human-in-the-loop) or AFK (autonomous) based on decision requirements
- Identifies dependencies and blocking relationships between slices
- Generates issue tracker-ready tickets with acceptance criteria and parent references
- Validates granularity and dependency structure through interactive user feedback
How to install to-issues
npx skills add https://github.com/vinvcn/mattpocock-skills-zh-cn --skill to-issues- Issue tracker access (GitHub, Jira, or similar)
- Issue tracker triage label vocabulary configured (or run `/setup-matt-pocock-skills`)
- Codebase context available for understanding current state
How to use to-issues
- 1.Provide the plan, spec, PRD, or issue reference you want to decompose
- 2.The skill will explore codebase context if needed to understand current state
- 3.Review the proposed vertical slices breakdown showing title, type (HITL/AFK), blockers, and user stories
- 4.Provide feedback on granularity, dependencies, and classifications
- 5.Approve the breakdown, then the skill publishes issues to your tracker in dependency order
Use cases
- Convert a product spec or PRD into a sequence of independently-assignable implementation issues
- Break down a feature plan into thin vertical slices that each deliver end-to-end value
- Create implementation tickets that span schema, API, UI, and tests in a single slice
- Identify which work requires human decisions (HITL) versus what can be automated (AFK)
- Engineering managers planning feature rollouts
- Tech leads breaking down specifications into implementation work
- Teams using issue trackers (GitHub, Jira, etc.) for work management
- Agents or developers implementing features slice-by-slice
to-issues FAQ
HITL (human-in-the-loop) slices require human decisions like architecture reviews or design approvals before implementation. AFK (away from keyboard) slices can be implemented and merged without human intervention. The skill prioritizes AFK slices when possible.
Each slice should be a complete end-to-end path through all layers (schema, API, UI, tests) but as narrow in scope as possible. Prefer many thin slices over fewer thick ones—each should be independently demonstrable or verifiable.
Yes, you can modify individual issues after creation. However, the skill will not close or modify the parent issue it was decomposing.
The skill will work with your feedback during the quiz phase to adjust granularity, merge slices, or split them further until the breakdown matches your needs.
Full instructions (SKILL.md)
Source of truth, from vinvcn/mattpocock-skills-zh-cn.
name: to-issues description: 使用 tracer-bullet vertical slices，把 plan、spec 或 PRD 拆成项目 issue tracker 上可独立领取的 issues。Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
To Issues
使用 vertical slices（tracer bullets）把计划拆成可独立领取的 issue tracker issues。
Issue tracker 和 triage label vocabulary 应该已经提供给你；如果没有，运行 /setup-matt-pocock-skills。
Process
1. Gather context
基于 conversation context 中已有内容工作。如果用户传入 issue reference（issue number、URL 或 path）作为参数，从 issue tracker 获取它，并读取完整 body 和 comments。
2. Explore the codebase (optional)
如果还没探索 codebase，就先探索，以理解代码当前状态。Issue titles 和 descriptions 应使用项目 domain glossary vocabulary，并遵守相关 ADRs。
3. Draft vertical slices
把计划拆成 tracer bullet issues。每个 issue 都是一个薄 vertical slice，end-to-end 穿过所有 integration layers，而不是某一层的 horizontal slice。
Slices 可以是 HITL 或 AFK。HITL slices 需要人类交互，例如 architecture decision 或 design review。AFK slices 可以无人交互地实现并合并。尽可能优先 AFK。
4. Quiz the user
把 proposed breakdown 作为编号列表展示。每个 slice 显示：
- Title：短描述名
- Type：HITL / AFK
- Blocked by：哪些其他 slices 必须先完成（如果有）
- User stories covered：覆盖哪些 user stories（如果 source material 中有）
询问用户：
- Granularity 是否合适？（too coarse / too fine）
- Dependency relationships 是否正确？
- 是否需要 merge 或继续 split 某些 slices？
- HITL 和 AFK 标记是否正确？
迭代直到用户批准 breakdown。
5. Publish the issues to the issue tracker
对每个批准的 slice，把新 issue 发布到 issue tracker。使用下面的 issue body template。这些 issues 被视为已准备好给 AFK agents 接手；除非另有指示，发布时应用正确的 triage label。
按 dependency order 发布 issues（blockers first），这样可以在 "Blocked by" 字段引用真实 issue identifiers。
<issue-template> ## Parent对 issue tracker 中 parent issue 的引用（如果 source 是现有 issue；否则省略本 section）。
What to build
这个 vertical slice 的简洁描述。描述 end-to-end behavior，不要按 layer-by-layer implementation 描述。
避免具体 file paths 或 code snippets；它们很快会过时。例外：如果 prototype 产出的 snippet 比 prose 更精确地编码了某个决策（state machine、reducer、schema、type shape），可以内联在这里，并简短说明它来自 prototype。保留决策密集部分，不要放完整 working demo。
Acceptance criteria
- Criterion 1
- Criterion 2
- Criterion 3
Blocked by
- 对 blocking issue 的引用（如果有）
如果没有 blocker，写 "None - can start immediately"。
</issue-template>不要 close 或 modify 任何 parent issue。
Related skills
More from vinvcn/mattpocock-skills-zh-cn and the wider catalog.
to-prd
Convert conversation context into a structured PRD and publish to your project issue tracker.
triage
Triage issues through state machines with category and state roles for bug and enhancement management.
ubiquitous-language
从当前 conversation 提取 DDD-style ubiquitous language glossary，标记 ambiguities 并提出 canonical terms。保存到 UBIQUITOUS_LANGUAGE.md。Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
write-a-skill
Create well-structured agent skills with progressive disclosure and bundled resources.
writing-beats
Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.
writing-fragments
Grilling session that mines the user for fragments — heterogeneous nuggets of writing (claims, vignettes, sharp sentences, half-thoughts) — and appends them to a single document as raw material for a future article. Use when the user wants to develop ideas before imposing structure, or mentions "fragments", "ideate", or "raw material" for writing.