Decompose project plans into structured vertical slice issues with HITL/AFK classification.
npx skills add https://github.com/docs-plus/docs.plus --skill to-issues-docs-plus
Please help me install this Agent Skill. Skill: to-issues Source: https://github.com/docs-plus/docs.plus/tree/main/.agents/skills/to-issues Command: npx skills add https://github.com/docs-plus/docs.plus --skill to-issues-docs-plus
Manually breaking down project plans, specs, or PRDs into unstructured, poorly dependent issues leads to messy tracking, blocked work, and tickets that can't be delivered independently. This Skill eliminates that friction by enforcing end-to-end vertical slice decomposition.
Use the to-issues skill to break down the attached product PRD for the new user notification system into trackable vertical slice issues for the engineering team.
High-intent search queries and answers about installing and using this skill.
To break down a product requirement document into trackable issues, you can automate the decomposition of project plans into structured vertical slices that cut across all integration layers for iterative development cycles.
Vertical slices in issue tracking are end-to-end tracer bullet tickets that cut through all integration layers like schema, API, and UI. You need them to ensure work is independently deliverable and fully demoable without blockers.
Splitting a PRD into independently deliverable tickets requires generating structured, assignable issues with clear dependency ordering and standardized templates, enforcing end-to-end vertical slice decomposition to eliminate blocked work.
Classifying development tickets by human involvement requires labeling slices as HITL (requires human input like design reviews) or AFK (can be implemented and merged without human intervention) to clarify workflow dependencies.
The best way to structure agile planning tickets for parallel work is generating thin, assignable tracer bullet issues with dependency ordering and standardized templates, enabling iterative, demoable development cycles without blockers.
Work breakdown for issue trackers supports both software development and product management workflows by decomposing project plans into structured, independently assignable issues with clear HITL/AFK classification and dependency ordering.
sumpalabsBreak down project plans and PRDs into assignable issues with acceptance criteria.
ruskibeatsConvert project plans, specifications, or PRDs into structured issues.
anonymousminatiBreak plans into dependency-ordered tracer-bullet issues with acceptance criteria.
akillnessConvert plans, specs, or requirements into vertical slice issues.
