← ClaudeAtlas

prd-reviewlisted

Adversarial PRD review using 5 specialized subagent personas. Probes for ambiguities, hidden complexity, and untestable requirements before execution begins. Use when: user says 'review this PRD', 'critique this spec', 'is this PRD ready', 'adversarial review', or when /prd-writer invokes it at Step 7. Also trigger when user shares an existing PRD and asks if it's implementation-ready.
closetmusician/claude-setup · ★ 0 · Code & Development · score 48
Install: claude install-skill closetmusician/claude-setup
## Required Files - `references/persona-prompts.md` — System prompts for 5 reviewer personas # PRD Review Four-phase adversarial review that catches spec ambiguities before agents hit them during implementation. Spawns 5 fresh subagents — each sees ONLY the PRD, no conversation history — to probe from different expert perspectives. **Model discipline:** This skill is Opus-heavy by design. The synthesis subagent (Phase 3), Triage (Phase 4.1) AND main agents MUST run as `model: opus`. Phase 2 subagents and others can run on Sonnet. **Context discipline:** Phase 2 subagents write their findings to disk. Phases 3 and 4 subagents read files from disk — they never receive raw Phase 2 outputs in context. The main agent reads only the final triage doc, keeping its context window thin. ## Core Principle A PRD is ready for implementation when an agent can build every requirement without a single AskUserQuestion call. Every ambiguity caught here saves a blocked subagent, a wrong guess, or a rework cycle during BUILD. --- ## Workflow ### Step 0: Locate the PRD and Set Up Working Directory Determine the PRD file path: **If invoked with a path** (e.g., `/prd-review docs/my-feature.md`): - Read the file. Confirm it exists and looks like a PRD. **If invoked from /prd-writer:** - The PRD path was passed in context. Read it. **If invoked standalone with no path:** - Search for recent PRD files: ```bash find . -maxdepth 3 -name "*.md" -newer .git/HEAD -type f 2>/dev/null | he