Breaks a plan into dependency-ordered, tracer-bullet vertical-slice issues.
npx skills add https://github.com/ayehiaa/my-travel-assistant --skill to-issues-ayehiaa
Please help me install this Agent Skill. Skill: to-issues Source: https://github.com/ayehiaa/my-travel-assistant/tree/main/.claude/skills/to-issues Command: npx skills add https://github.com/ayehiaa/my-travel-assistant --skill to-issues-ayehiaa
Breaks a plan, spec, or PRD into a set of small, end-to-end implementation tickets so work can be scheduled, built, and verified incrementally on the project issue tracker.
Use to-issues to convert the plan currently described in the conversation into a numbered list of tracer-bullet issue drafts, quiz for granularity and dependencies, and then publish the approved slices to the issue tracker with the correct triage label.
High-intent search queries and answers about installing and using this skill.
To break a PRD into GitHub issues, the Skill converts continuous delivery goals into independently grabbable tracer-bullet vertical slices. Each issue cuts through schema, API, UI, and tests end-to-end so work can be scheduled and verified incrementally.
A tracer-bullet vertical slice is a narrow, complete implementation path cutting through all integration layers like schema, API, UI, and tests. This technique ensures each issue delivers end-to-end functionality that can be built and verified independently.
Dependency mapping identifies what must be completed first and marks dependencies using a Blocked by field on each issue. This ensures teams start implementation in the correct order and can easily see which tickets are unblocked.
Yes, you can label issues as HITL needing human interaction like design review or AFK meaning they can be implemented and merged without human input. This HITL/AFK classification helps triage and planning by sizing slices appropriately.
Yes, to-issues publishes approved tracer-bullet issues to the project tracker in strict dependency order. It uses a standardized issue body template so downstream agents can execute the tickets reliably without missing context.
You should not use tracer-bullet issue breakdown when your plan lacks clear integration layers or end-to-end verification paths. The approach requires slicing through schema, API, and UI together, making it unsuitable for isolated single-layer tasks.
xenitV1Enforce backend design patterns for scalable systems with vertical slice architecture.
LevezzeConvert PRDs into dependency-ordered GitHub issues with tracer-bullet slices.
kartikkabadiBreak plans, specs, or PRDs into dependency-ordered issues with acceptance criteria.
vessuxBreak plans, specs, or PRDs into independent issue tickets with tracer-bullet vertical slices.
