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.
Install
npx skills add javimosch/supercli --skill to-issuesgit clone --depth 1 https://github.com/javimosch/supercli.git /tmp/supercli
mkdir -p ~/.claude/skills
cp -r /tmp/supercli/.agents/skills/to-issues ~/.claude/skills/to-issuesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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> - Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests) - A completed slice is demoable or verifiable on its own - Prefer many thin slices over few thick ones </vertical-slice-rules> ### 4. Quiz the user
Details
- Skill name
to-issues- Repository
- javimosch/supercli
- Path
.agents/skills/to-issues/SKILL.md- License
- MIT
- Repo updated
- 2 November 2026
- Listed in
- heilcheng/awesome-agent-skills
FAQ
What does the To Issues skill do?
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.
How do I install the To Issues skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add javimosch/supercli --skill to-issues. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is To Issues popular?
It lives in javimosch/supercli, which has 57 GitHub stars and 5 forks, and is included in 1 curated skill list.
Related skills
100 Exercises to Learn Rust
57javimosch/supercli
Use this skill when the user wants to use 100-exercises-to-learn-rust.
2to3
57javimosch/supercli
Use this skill when the user wants to use 2to3, cli tool: 2to3.
2to3 2.7
57javimosch/supercli
Use this skill when the user wants to use 2to3-2.7, cli tool: 2to3-2.7.
To Prd
57javimosch/supercli
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
SpaghettiKart
57javimosch/supercli
Use this skill when the user wants to use SpaghettiKart for I have spaghetti, now i just need a kart.
Topit
57javimosch/supercli
Use this skill when the user wants to use Topit for Pin any window to the top of your screen / 在Mac上将你的任何窗口强制置顶.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.