skills.rest
benjr70
benjr70COMMUNITY
Explore all skills by this author →
GitHub

to-tickets

Breaks specs into vertical slices and publishes them as GitHub issues with dependencies.

1|1|Updated Oct 3, 2021
Search Tags:#github issues#gh cli#project automation#spec breakdown#vertical slices#ticket planning#dependency edges
One-click install
npx skills add https://github.com/benjr70/Smart-Smoker-V2 --skill to-tickets-benjr70
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/benjr70/Smart-Smoker-V2/tree/main/.claude/skills/to-tickets
Command: npx skills add https://github.com/benjr70/Smart-Smoker-V2 --skill to-tickets-benjr70

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written spec or plan into actionable, correctly-sequenced GitHub issues is tedious and error-prone: dependencies get missed, labels are inconsistent, and tickets end up invisible to automation. This Skill automates the breakdown of a Spec into tracer-bullet vertical slices and publishes them as fully wired GitHub issues. ## Core Features & Use Cases - Vertical slice drafting: Cuts each Slice through every layer (schema, API, UI, tests) so each one is independently demoable, with expand-contract sequencing for wide refactors. - GitHub issue publishing: Creates one issue per Slice from a fixed template, wires native blocked-by dependency edges, and links each Slice as a sub-issue of the parent Spec. - AFK/HITL triage and project setup: Labels Slices as AFK (agent-pickable) or HITL (human needed), bootstraps twelve labels idempotently, and adds AFK Slices to Project #1 with a Priority. - Use Case: After writing a Spec issue for a new feature, run the Skill with the spec number to get a reviewed set of implementation tickets with correct blocking edges, ready for an agent daemon to pick up. ## Quick Start Ask the AI to break spec issue number 123 into implementation tickets using the to-tickets workflow, optionally with dry-run to preview first.

Frequently Asked Questions about to-tickets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break a spec into GitHub issues automatically?▼

Invoke the Skill with a spec issue number or URL, and it drafts vertical slices, quizzes you on granularity and priority, then creates one GitHub issue per slice with blocking edges and sub-issue links. Use --dry-run to preview everything without mutating the tracker.

What is a vertical slice in ticket planning?▼

A vertical slice cuts a narrow but complete path through every layer (schema, API, UI, tests) so it is demoable on its own, unlike a horizontal slice of one layer. Each slice is sized to fit in a single fresh context window.

Does the Skill support a dry run before creating issues?▼

Yes, the --dry-run flag prints the planned issue titles, types, blockers, full bodies, and the commands that would run, then stops. It creates no issues, labels, project items, or dependency edges.

How are GitHub issue dependencies wired between tickets?▼

The Skill uses the GitHub API endpoint issues/<n>/dependencies/blocked_by with the numeric database id of the blocker, plus sub_issues to link each slice to the parent spec. Both endpoints are idempotent-ish, so duplicate edges are safe to ignore.

What is the difference between AFK and HITL labels?▼

AFK marks slices an agent daemon can implement and merge without human involvement; HITL marks slices needing live human judgement such as architectural decisions or credential handling. Only AFK slices are added to Project #1, since project membership is the daemon's pick-up signal.

When should wide refactors not be sliced vertically?▼

Wide refactors, where one mechanical change breaks thousands of call sites, cannot land green as vertical slices. The Skill sequences them as expand-contract: add the new form, migrate call sites in batches, then delete the old form.

Related Skills

Explore More Software Engineering Skills→
Harmeet10000Harmeet10000
7

prd-to-issues

Break PRDs into GitHub issues with tracer-bullet vertical slices.

Community
Advanced
cloudofgeorgecloudofgeorge

triage

Move GitHub issues and external PRs through a labeled triage state machine.

Community
Advanced
pacaplanpacaplan
30

flokay:wait-ci

Poll GitHub CI check and pull request review statuses for the current branch.

Community
Advanced
cookeyholdercookeyholder

planning-and-task-breakdown

Decomposes complex projects into verifiable tasks with explicit acceptance criteria.

Community
Intermediate