Break specs and ADRs into epic and work stream tracker issues.
npx skills add https://github.com/arthur-debert/dodot --skill to-tickets-arthur-debert
Please help me install this Agent Skill. Skill: to-tickets Source: https://github.com/arthur-debert/dodot/tree/main/.agents/skills/to-tickets Command: npx skills add https://github.com/arthur-debert/dodot --skill to-tickets-arthur-debert
This Skill helps turn a written spec into a practical set of tracker issues so teams can move from planning to execution without losing the original intent.
Ask the assistant to break your spec into epic and work-stream tickets for the project issue tracker.
High-intent search queries and answers about installing and using this skill.
To turn a spec into shippable issue tickets, you break the spec and its ADRs into an execution-tracking epic issue and independently shippable work stream sub-issues. This structures your feature implementation into sequenced tracker tickets.
Tracer-bullet slicing for issue tracker setup is the process of breaking down feature implementation into thin, end-to-end vertical slices. This produces independently shippable work stream sub-issues that can be tracked and shipped sequentially.
You create epic issues from ADRs and spec documents by summarizing the feature into an execution-tracking epic issue. This requires aligning authoritative spec documents and ADR references with your project issue taxonomy to produce publishable ticket metadata.
Yes, ADR references are required to generate work stream sub-issues. The process requires alignment with authoritative spec documents and ADR references alongside the project issue taxonomy to accurately slice and publish tracker tickets.
The best way to break feature specs into sequenced tracker tickets is applying vertical slice work stream breakdown. This distinguishes itself by structuring titles, dependencies, and acceptance criteria into ready-to-create issues rather than generic task lists.
You should not use epic and work-stream ticket generation when you lack authoritative spec documents or established ADR references. Without aligned project issue taxonomy and foundational spec metadata, the generated ticket dependencies and acceptance criteria will be inaccurate.
danielcastro-devDraft collaborative feature plans with clarifying questions to .speclet/draft.md.
charly-vibesConvert markdown implementation plans into linked issues with dependencies.
J03Fr0stConvert project plans and specifications into structured issue tracker tickets.
jclfocusedA new style of educational software. Featuring:
