Convert product requirement documents into GitHub issues via vertical slices.
npx skills add https://github.com/onblueroses/strata --skill to-issues-onblueroses
Please help me install this Agent Skill. Skill: to-issues Source: https://github.com/onblueroses/strata/tree/main/skills/to-issues Command: npx skills add https://github.com/onblueroses/strata --skill to-issues-onblueroses
This Skill assists in breaking down PRDs, plans, or specs into a structured set of GitHub issues for tracking work outside of sessions.
gh CLI to publish issues into GitHub trackers.To create issues from a PRD, use the command: /to-issues /path/to/your/prd.md
High-intent search queries and answers about installing and using this skill.
This Skill transforms product requirement documents into GitHub issues using a vertical slice approach. It breaks down plans into demoable units of work and uses a draft-approve workflow before publishing to your repository.
The vertical slice approach for issue management breaks down plans into vertical slices that are demoable on their own. This allows cross-functional teams to track software development tasks as independent, functional deliverables within GitHub.
To create GitHub issues from a spec file, use the command `/to-issues /path/to/your/prd.md`. This processes the document and uses the GitHub CLI to publish the approved issues directly into your GitHub trackers.
Yes, you need the GitHub CLI to publish drafted issues to your repository. This Skill uses the `gh` CLI integration to publish the approved issues directly into GitHub trackers for cross-functional team tracking.
Yes, you can review and approve issues before they are published to GitHub. The draft-approve workflow allows you to draft issues, reference other slices, and approve them before they are published to your repository trackers.
A limitation of using vertical slicing for cross-functional team tracking is that it requires your plans or specs to be clearly defined into demoable units. If your PRD lacks structural boundaries, generating independent vertical slices for GitHub issues may be difficult.
albertattardConvert product requirement documents into sequential Markdown vertical slices.
gabergerAutomate GitHub project governance with swarm coordination for issues, boards, and sprints.
joeczarFetch GitHub milestones and issues to compute completion percentages.
haryelramalhoBreak plans, specs, and PRDs into dependency-ordered project issues.