Break down project plans and PRDs into assignable issues with acceptance criteria.
npx skills add https://github.com/sumpalabs/petrodb --skill to-issues-sumpalabs
Please help me install this Agent Skill. Skill: to-issues Source: https://github.com/sumpalabs/petrodb/tree/main/.agents/skills/to-issues Command: npx skills add https://github.com/sumpalabs/petrodb --skill to-issues-sumpalabs
Manually breaking down project plans, specifications, and product requirement documents into well-scoped, independently assignable issues for issue trackers is time-consuming and often results in poorly defined, overlapping, or overly large tickets that slow down development workflows.
Use the to-issues skill to break down the attached Q4 feature PRD into vertically-sliced, trackable issues for the project issue tracker.
High-intent search queries and answers about installing and using this skill.
To break down a PRD into trackable issues, decompose the specifications into independently assignable vertical slices. This generates structured tickets with acceptance criteria, dependency tracking, and triage labels for your issue tracker.
Vertical slices in agile project breakdown are thin, end-to-end work segments cutting through all integration layers like schema, API, UI, and tests. This tracer bullet approach ensures each issue delivers a complete, demoable piece of functionality.
Generate tickets with clear dependency relationships from a project plan by decomposing the work into demoable vertical slices. This creates structured issues featuring acceptance criteria, blocker references, and triage labels adhering to tracer bullet principles.
Yes, you can automatically label issue slices as human-in-the-loop or AFK during ticket creation. This HITL/AFK slice classification streamlines workflow prioritization by identifying slices that need architectural decisions versus those mergeable without human interaction.
The best way to decompose product requirements into demoable work tickets is applying tracer bullet principles to create vertical slices. This ensures end-to-end verifiability and generates ready-to-publish issues with pre-filled acceptance criteria and dependency tracking.
Use vertical slices instead of horizontal layers for work decomposition to ensure each issue delivers complete, demoable functionality. Vertical slices cut through all integration layers, preventing poorly defined, overlapping, or overly large tickets that slow development workflows.
MatheusBBarniBreak plans, specs, or PRDs into tracer-bullet vertical slice issues.
henrycashe26Break project plans and PRDs into vertical slice issues with acceptance criteria.
HerxinsasaBreak down project plans into vertical slice issue tracker tickets.
docs-plusDecompose project plans into structured vertical slice issues with HITL/AFK classification.
