Break PRDs and plans into tracker-ready issues with acceptance criteria.
npx skills add https://github.com/malinskibeniamin/skills --skill to-issues-malinskibeniamin
Please help me install this Agent Skill. Skill: to-issues Source: https://github.com/malinskibeniamin/skills/tree/main/to-issues Command: npx skills add https://github.com/malinskibeniamin/skills --skill to-issues-malinskibeniamin
Break PRD or plan into tracker issues as thin vertical slices to turn strategy into actionable work items that teams can start immediately.
Draft tracer-bullet slices that map the plan into independently grabbable, demoable issues.
High-intent search queries and answers about installing and using this skill.
To break a PRD into tracker-ready issues, the process decomposes product plans into thin, independently grabbable vertical slices. Each slice maps to a demoable issue with clear acceptance criteria, defined parent/child relationships, and standard templates for triage.
Splitting a product roadmap into thin vertical slices involves applying tracer-bullet decomposition to designs and plans. This generates a publishable issue backlog where each item is an independent, demoable work unit preserving the original planning order.
Yes, you can apply this issue breakdown process directly to design documents. It transforms designs into tracker-ready issues by mapping them into independent slices with defined parent/child relationships and standard templates for immediate team handoff.
Applying triage labels during issue tracking ensures dependencies are tracked and planning order is preserved. It transforms roadmaps and PRDs into a structured, publishable issue backlog ready for immediate team handoff and development.
Use tracer-bullet slices for issue breakdown when you need to turn strategy into actionable work items from large PRDs. It creates thin, demoable slices that teams can start immediately, ensuring each issue has clear acceptance criteria.
No, the issue breakdown process does not require a specific issue-tracking platform. It generates standard template issues with clear acceptance criteria and parent/child relationships that can be published to any standard issue tracker.
yukikmGenerate a Product Requirements Document draft from initial requirements.
anukkrit149Convert plans, specs, or PRDs into vertical-slice issues with needs-triage labels.
getty104Create GitHub Issues with parent-child and blocked-by dependencies from YAML input.
tomas-uGenerate prioritized product plans and quarterly roadmaps from reference documents.
