cc-skill:to-issues
Claude Code skill · anthropic · active
This skill takes a plan, spec, or product requirement and breaks it into small, independent work tickets called 'vertical slices.' Each slice goes all the way through the system (database, API, user interface, tests) so it can be completed and tested on its own.
Product managers, tech leads, and founders who need to turn a big feature plan into a list of concrete tasks their team can grab and build.
When someone asks to break down a plan into issues, create implementation tickets, split work into tasks, or convert a spec into a list of work items.
- "Break this product roadmap into implementation issues for our team"
- "Convert this PRD into independently grabbable work tickets"
- "Create implementation issues for the user authentication feature"
You know it worked because it presents a clear list of small, end-to-end work slices (not just database work or just UI work), asks clarifying questions about the breakdown, and then creates new tickets in your issue tracker once you approve it.
Deploy this skill
no laptop requiredRun this skill on a schedule in the cloud. Pipe output to Telegram, email, or any webhook. Every run is logged here with full output, cost, and thumbs feedback.
How this performs
Cloud-automation runs, real outputs, and feedback.
No cloud runs yet for this skill.
Once you deploy it (above), every run will show up here with the actual output, exact cost, and a thumbs button so you can rate quality over time.
Claude Code skill at /Users/olanrewajukareem/.claude/skills/to-issues/SKILL.md. Auto-triggered by description matching when you type in Claude Code, OR embedded into agent system prompts (LeadFlow framework skills are wired this way). Auto-synced from disk every 6h via launchd.
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.
Local Claude Code use (optional)
Install the SKILL.md file locally so this skill is available the next time you open Claude Code on your Mac. Most users skip this and just use cloud deployments above.
Save this skill to ~/.claude/skills/to-issues/SKILL.md so Claude Code auto-loads it whenever its description matches your prompt.
{
"source": "global",
"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."
}{
"method": "embed_in_prompt",
"skill_path": "/Users/olanrewajukareem/.claude/skills/to-issues/SKILL.md"
}That means either: (a) the system has not had a task that matched its strengths, (b) a more cost-effective alternative was picked by the router, or (c) the related automation is toggled OFF on /automations. The Recommender reviews idle tools weekly and may suggest killing it.