Breaks plans and specs into tracer-bullet tickets with declared blocking edges.
npx skills add https://github.com/gmackie/agent-skills --skill to-tickets-gmackie
Please help me install this Agent Skill. Skill: to-tickets Source: https://github.com/gmackie/agent-skills/tree/main/skills/to-tickets Command: npx skills add https://github.com/gmackie/agent-skills --skill to-tickets-gmackie
.scratch/<feature-slug>/issues/ or as native blocking links on a real tracker like GitHub or Linear. - Expand-Contract Sequencing: Handles wide refactors (renames, retypes) that cannot be vertically sliced by sequencing them as expand, batched migration, and contract tickets. - Use Case: After drafting a feature spec, ask the agent to break it into tickets; it quizzes you on granularity and dependencies, then publishes approved tickets with a ready-for-agent triage label. ## Quick Start Break the attached feature spec into tracer-bullet tickets with blocking edges and publish them to my issue tracker.High-intent search queries and answers about installing and using this skill.
Provide the spec path, issue number, or URL and the skill drafts tracer-bullet tickets, each a vertical slice with declared blocking edges. After you approve the breakdown, it publishes one issue per ticket in dependency order with native blocking links where the platform supports them.
A vertical slice ticket cuts a narrow but complete path through every layer: schema, API, UI, and tests. Each completed slice is demoable on its own and sized to fit in a single fresh context window, unlike horizontal slices that cover only one layer.
Yes, the skill supports both. With a real tracker it creates one issue per ticket using native blocking or sub-issue relationships and applies the ready-for-agent label; without one it writes one markdown file per ticket under .scratch/<feature-slug>/issues/.
Each ticket declares which other tickets must complete before it can start. Tickets are published blockers-first so edges reference real identifiers, and any ticket whose blockers are all done forms the workable frontier.
Wide refactors, such as renaming a column or retyping a shared symbol, break thousands of call sites at once, so no vertical slice lands green. The skill sequences these as expand-contract: add the new form, migrate call sites in batches, then delete the old form.
AnasIsmai1Break plans and PRDs into vertical-slice issues on a project issue tracker.
subvisualGenerates implementation-ready delivery tickets with Gherkin acceptance criteria from requirements, PRDs, and specs.
darkmatterDetect shallow modules and propose deepening refactors using project glossary and ADRs.
GongYuanCaiJiExecutes small ad-hoc code changes with atomic commits and summary tracking.