Translate plans or PRDs into dependency-ordered GitHub issue tickets.
npx skills add https://github.com/spontus-reach/spontus --skill to-issues-spontus-reach
Please help me install this Agent Skill. Skill: to-issues Source: https://github.com/spontus-reach/spontus/tree/main/.agents/skills/to-issues Command: npx skills add https://github.com/spontus-reach/spontus --skill to-issues-spontus-reach
It helps teams convert a plan, spec, or PRD into a set of end-to-end issues that are small, testable, and straightforward to pick up.
Run the to-issues skill and provide the plan/spec/PRD text you want broken down so it can propose and then publish the vertical-slice issues to the project tracker.
High-intent search queries and answers about installing and using this skill.
To break a product specification into GitHub issues, you translate the PRD into vertical tracer-bullet slices. This decomposes work into thin end-to-end units across schema, API, UI, and tests so each implementation ticket is verifiable on its own.
Vertical slice issue decomposition splits a roadmap into tracer-bullet issues that cut through all integration layers. You use it for roadmap-to-execution workflows when work must be split into thin end-to-end units that are small and straightforward to pick up.
Sequencing implementation tickets by dependencies involves applying dependency-aware grouping to the vertical slices. This records which slices must happen first and publishes the issues to the GitHub issue tracker in a blocker-first order.
Yes, you can label GitHub issues to distinguish autonomous work from human interaction by applying HITL versus AFK classification. This separates slices needing architectural or design reviews from those that can be implemented and merged autonomously.
Converting a PRD into GitHub issues automatically generates issue-body formatting with acceptance criteria. It aligns the implementation tickets to the project’s domain vocabulary and triage label conventions without requiring manual acceptance criteria writing.
sadie100Generate a Product Requirements Document from conversation context and codebase insights.
oxieBreak down implementation plans into 20-30 testable tasks with acceptance criteria.
Minara-AIDecompose project plans into granular issues with acceptance criteria and dependency mapping.
HerxinsasaBreak down project plans into vertical slice issue tracker tickets.
