Break plans, specs, or PRDs into dependency-ordered issues with acceptance criteria.
npx skills add https://github.com/kartikkabadi/skills --skill to-issues-kartikkabadi
Please help me install this Agent Skill. Skill: to-issues Source: https://github.com/kartikkabadi/skills/tree/main/to-issues Command: npx skills add https://github.com/kartikkabadi/skills --skill to-issues-kartikkabadi
This Skill helps you transform a plan, spec, or PRD into clear, independently actionable issues for an issue tracker, so work can be split into manageable slices instead of vague tasks.
Use the to-issues skill to break this PRD into independently grabbable issues with dependencies and acceptance criteria.
High-intent search queries and answers about installing and using this skill.
To break a PRD into actionable issues, you decompose broad requirements into vertical slices that span the full stack end to end, adding dependency ordering and acceptance criteria so each issue can be grabbed independently.
Vertical slice decomposition in product planning is the process of converting broad requirements into tracer-bullet issues that each span the full stack end to end, ensuring every slice delivers independent, testable value.
Ordering implementation tickets by dependencies requires iterative dependency sequencing, ensuring blockers are handled first so downstream work can be published with correct references to preceding issues.
Yes, you can classify issue tracker tickets by distinguishing between human-in-the-loop and automatable slices, which validates workflow assignments before publishing the issues to the team.
Yes, generating issue-ready acceptance criteria is required for every issue slice to ensure the decomposed work is independently verifiable and meets the defined product spec before publishing.
The best way to split a spec into manageable tasks is applying vertical slice breakdown to produce independently grabbable issues, complete with iterative dependency ordering and clear acceptance criteria.
RDCrystalLabConvert product requirement documents into structured GitHub implementation issues.
kenlckExecute a tracker issue end-to-end with TDD until acceptance criteria are met.
HerxinsasaBreak down project plans into vertical slice issue tracker tickets.
ThorStarlordBreak plans into dependency-ordered issue tracker tickets with triage labels.
