to-issues
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
Best for plan-to-issue conversionWorks with GitHubLow risk
⌘source
- author
@mattpocock- language
- Shell
★36kstars
2.9kforks
Apr 29, 2026
✦overview.md
Key Features
- ·Breaks plans into vertical-slice issues
- ·Supports HITL and AFK slice types
- ·Fetches issue context from tracker
- ·Explores codebase for domain vocabulary
- ·Respects ADRs and existing labels
Use Cases
- →Convert a product spec into actionable issues for a sprint
- →Break down a large PRD into independently-grabbable implementation tasks
- →Transform a high-level plan into tracer-bullet issues for team assignment
Best for
- ✓plan-to-issue conversion
- ✓sprint planning
- ✓vertical slicing
Not ideal for
- !already-tracked issues
- !non-code projects
FAQs
name
to-issues
description
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
To Issues
Break a plan into independently-grabbable issues using vertical slices (tracer bullets).
The issue tracker and triage label vocabulary should have been provided to you — run /setup-matt-pocock-skills if not.
Process
1. Gather context
Work from whatever is already in the conversation context. If the user passes an issue reference (issue number, URL, or path) as an argument, fetch it from the issue tracker 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. Issue titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.
3. Draft vertical slices
Break the plan into tracer bullet issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.
Slices may be 'HITL' or 'AFK'. HITL slices require human interaction, such as an architectural decision or a design review. AFK slices can be implemented and merged without human interaction. Prefer AFK over HITL where possible.
<vertical-slice-rules>$install
1-click copynpx skills add mattpocock/skills --skill to-issuesSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
4/ 5
highMostly actionable with clear steps; only a few small gaps remain.