review-prd
This skill is invoked when the user wants to review a PRD before breaking it into issues. You spawn two specialized subagents for complementary perspectives, then consolidate their feedback into actionable edits.
-
Locate the plan. The plan lives at
plans/<plan-name>/. If the user specified the plan name, use it. Otherwise list all folders insideplans/: if there is exactly one, use it automatically; if there are multiple, ask the user which plan to review. -
Read materials. Read
plans/<plan-name>/README.md(the PRD) andAGENTS.mdat the repo root (if it exists — used as system prompt context). -
Spawn the Product/Design Review subagent with the following instructions (include
AGENTS.mdas system context if it exists):Flag:
- Gaps — user stories or flows that are mentioned but never fully specified
- Contradictions — places where two sections of the PRD disagree
- Undefined edge cases — what happens when things go wrong or inputs are unexpected?
- Missing acceptance criteria — how would an engineer know they're done?
- Ambiguous scope boundaries — what's in and what's out?
Be specific and cite the relevant section. Vague concerns like "needs more detail" without saying what detail is missing are not useful.
More from rodrigooslp/skills
work-on-issue
Implement a documented issue file end-to-end — read the right context, do only the in-scope work, run quality gates, mark the issue done, and produce a structured completion report. Use whenever the user asks you to implement, work on, or complete a numbered issue — for example "work on issue 004", "implement issue 012", or "you're agent on issue 007".
11prd-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.
7review-issues
Review an issue set by spawning two subagents (one for implementer review, one for PRD-coverage review), consolidating their feedback into actionable items. Use when the user wants to review issues, validate the issue breakdown, check issues against the parent PRD, or mentions "review issues".
5use-conventional-commits
>
5merge-branch
Merge an issue branch into the current branch via `--no-ff` (never squash), remove its registered worktree at `./worktrees/<plan>/<id>` if any, and delete the merged branch locally. Use when the user asks to merge an issue branch — for example "merge-branch 6", "merge issue 12 in", or "bring issue 7 from the auth plan into this branch".
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.
4