Breaks plans and specs into tracer-bullet tickets with declared blocking edges.
npx skills add https://github.com/j172/bid --skill to-tickets-j172
Please help me install this Agent Skill. Skill: to-tickets Source: https://github.com/j172/bid/tree/main/agent/skills/to-tickets Command: npx skills add https://github.com/j172/bid --skill to-tickets-j172
High-intent search queries and answers about installing and using this skill.
Provide the spec path, issue URL, or work from the current conversation, and the Skill drafts vertical tracer-bullet slices. Each ticket declares its blocking edges, and you review granularity and dependencies before anything is published.
A vertical slice cuts a narrow but complete path through every layer — schema, API, UI, and tests — rather than one horizontal layer. Each completed slice is demoable or verifiable on its own and sized to fit a single context window.
Yes, the Skill publishes to whatever tracker the setup command configured. Local mode writes one Markdown file per ticket under .scratch, while real trackers get native blocking links and a ready-for-agent triage label.
Wide refactors use expand-contract sequencing: add the new form beside the old, migrate call sites in blast-radius-sized batches as separate blocked tickets, then delete the old form last. Batches can share an integration branch when they cannot stay green alone.
File paths and code go stale quickly as the codebase evolves, making tickets misleading. The exception is prototype snippets that encode a decision — like a state machine or type shape — which may be inlined with a note about their origin.
lapaixkemsdortshlee-svgShape vague product ideas into clear design directions before implementation.
MaxWolf-01Breaks a grilled specification into dependency-ordered tracer-bullet ticket files with blocking edges.
cropsggStandardize domain terminology across projects using CONTEXT.md and ADRs.
jacksonlee-twDecomposes specifications into ordered, verifiable implementation tasks with acceptance criteria.
