prd-to-issues
This skill is invoked when the user wants to break a PRD into implementation issues. The PRD lives at plans/<plan-name>/README.md. You produce numbered issue files under plans/<plan-name>/issues/ plus an index.json tracker.
-
Locate the PRD. The PRD lives at
plans/<plan-name>/README.md. If the user hasn't specified the plan name and there is more than one folder insideplans/, ask them which one to use. If there is only one, use it. -
Explore the codebase (optional). If you have not already explored the codebase, do so to understand the current state of the code.
-
Draft vertical slices. Break the PRD into tracer-bullet issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.
Slices may be
HITL(require human interaction, such as an architectural decision or a design review) orAFK(can be implemented and merged without human interaction). Prefer AFK over HITL where possible.For each slice, assign an effort level from 1-5 using the rubric in REFERENCE.md. The level reflects how much reasoning and design judgement the issue requires, which downstream tooling uses to route the issue to an appropriately capable model.
-
Quiz the user. Present the proposed breakdown as a numbered list. For each slice, show:
More from rodrigooslp/skills
work-on-issue
>
10use-conventional-commits
>
5review-issues
Review an issue set by spawning two subagents (one for implementor review, one for PRD-coverage review), consolidating their feedback into actionable items. Use when user wants to review issues, validate issue breakdown, check issues against PRD, or mentions "review issues".
4write-a-prd
Create a PRD through user interview, codebase exploration, and module design, then save it to the plans folder. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
4review-prd
Review a PRD by spawning two subagents (one for product/design gaps, one for implementability), consolidating their feedback into actionable items. Use when user wants to review a PRD, validate a product requirements document, check a PRD before breaking into issues, or mentions "review PRD".
4merge-branch
>
3