review-issues
Review Issues
Review an issue set by spawning two specialized subagents for complementary perspectives, then consolidate feedback into actionable edits.
Process
1. Locate the plan
The plan lives at plans/<plan-name>/. If the user specified the plan name, use it. Otherwise:
- List all folders inside
plans/ - If there is exactly one, use it automatically
- If there are multiple, ask the user which plan to review
2. Read all materials
Read:
More from rodrigooslp/skills
work-on-issue
>
10prd-to-issues
Break a PRD into independently-grabbable issues using tracer-bullet vertical slices, saved as markdown files in the plan's `issues/` folder along with an `index.json` tracker. Use when the user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.
7use-conventional-commits
>
5write-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