Convert PRDs into vertical-slice GitHub issues with dependencies.
npx skills add https://github.com/raphaelmans/agent-skills --skill prd-to-issues-raphaelmans
Please help me install this Agent Skill. Skill: prd-to-issues Source: https://github.com/raphaelmans/agent-skills/tree/main/prd-to-issues Command: npx skills add https://github.com/raphaelmans/agent-skills --skill prd-to-issues-raphaelmans
Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices, enabling teams to plan, track, and implement PRD-driven work efficiently.
Provide the PRD GitHub issue number or URL, and instruct the AI to draft tracer-bullet vertical slices as GitHub issues.
High-intent search queries and answers about installing and using this skill.
To break a PRD into GitHub issues, provide the PRD issue URL to generate tracer-bullet vertical slices. Each slice covers all layers (schema, API, UI) and includes user stories, acceptance criteria, blockers, and dependencies for independent tracking.
Vertical slices in project management are end-to-end tracer bullet segments that traverse all layers (schema, API, UI, tests) to be independently testable. They ensure each slice delivers functional value across the entire stack rather than focusing on a single horizontal layer.
Creating tracer bullet slices with dependencies involves classifying slices as HITL or AFK types and defining blocker relationships to ensure correct sequencing. This structured plan converts product requirements into executable GitHub issues with clear execution order.
Yes, PRD breakdown using tracer-bullet vertical slices explicitly manages blockers and slice sequencing. It classifies slices as HITL or AFK types and defines dependency relationships among slices to ensure correct implementation order and trackable progress.
Yes, you can convert an existing PRD GitHub issue into structured user stories and acceptance criteria. Supply the GitHub issue number or URL to map product requirements into actionable issues with aligned user stories and clear acceptance criteria.
The best way to structure GitHub issues for end-to-end implementation is using vertical slices that cover all layers (schema, API, UI, tests). This ensures each issue is independently testable, includes acceptance criteria, and maps directly to user stories from the PRD.
tomholfordBreak a PRD into dependency-ordered GitHub issues using vertical slices.
xenitV1Enforce backend design patterns for scalable systems with vertical slice architecture.
MomoDavilukeConvert plans, specs, or PRDs into tracer-bullet issues on the project tracker.
a35506322Break project plans and PRDs into assignable vertical slice issues.
