Breaks a plan or spec into tracer-bullet tickets with declared blocking edges.
npx skills add https://github.com/MoofonLi/dev-ready --skill to-tickets-moofonli
Please help me install this Agent Skill. Skill: to-tickets Source: https://github.com/MoofonLi/dev-ready/tree/main/.agents/skills/to-tickets Command: npx skills add https://github.com/MoofonLi/dev-ready --skill to-tickets-moofonli
docs/handoff/<version>/phase-N/tickets/ with a Conventional Commit message, standing rules, and acceptance checkboxes. - Use Case: After accepting a spec in docs/specs/, run this Skill to produce a numbered, dependency-ordered set of ticket files that an engineer (or agent) can execute one at a time without further context. ## Quick Start Ask the agent to break the accepted spec in docs/specs into tracer-bullet tickets with blocking edges and publish them as individual ticket files.High-intent search queries and answers about installing and using this skill.
Provide the spec or plan as context, and the Skill drafts vertical tracer-bullet slices, each cutting through all layers (schema, API, UI, tests). You review the proposed breakdown, adjust granularity and blocking edges, then it publishes one file per ticket in dependency order.
A tracer-bullet ticket is a narrow but complete vertical slice through every layer of the stack, so the finished ticket is demoable on its own. It contrasts with horizontal slices that cover only one layer and cannot be verified independently.
Each ticket lists the tickets that block it in a 'Blocked by' field, and files are numbered from 01 in dependency order so blockers come first. Tickets with no blockers can start immediately, and execution works the frontier of unblocked tickets.
Only tickets marked parallel-safe: yes, meaning their file footprints are provably disjoint from every other open ticket. Parallel sessions each run in their own git worktree and deliver a patch back; sequential execution in the main tree is the default.
Wide refactors use an expand-contract sequence instead of a tracer bullet: add the new form beside the old, migrate call sites in blast-radius-sized batches, then delete the old form. Each phase becomes its own ticket with appropriate blocking edges.
Tickets are written as one Markdown file per ticket under docs/handoff/<version>/phase-N/tickets/, named NN-slug.md. The handoff tree is gitignored, so tickets are working files that are never committed.
wubing7755Stress-test plans, build domain models, and decompose large work into specs and tickets.
J0JngImplement work from a spec or tickets using TDD and code review.
richard-jh-mccraeBreaks plans or specs into tracer-bullet tickets with declared blocking edges published to a tracker.
redblacktreeExecutes ralph plan and implementation slash commands for a given ticket.