spec-peer-review — Claude Code skill: review specs
spec-peer-review runs one independent review of an approved spec, RFC, design document, or detailed PRD. It returns findings for the user to select.
no license 161 installs ★ 655 updated 2026-10-20
npx skills add pedronauck/skills --skill spec-peer-review -a claude-codeWhat spec-peer-review does
spec-peer-review examines a saved specification, design document, RFC, or detailed PRD when the user asks for an outside review. It follows linked contracts, examples, test expectations, ADR decisions, and instructions affecting the reviewed area. Each round gets its own peer-review-findings-roundN.md artifact.
The skill accepts extra context, an output directory, a reviewer runtime, a model, and a reasoning setting. It then checks the findings with scripts/validate-findings.sh, reports the verdict and limitations, and applies only the findings the user chooses. The review does not start on its own.
Implementation reviews and automatic approval loops are outside its scope. The independent pass can use an available native reviewer, a Compozy session, or herdr TUI. It does not approve designs, publish changes, or create commits.
What it helps with
- review an RFC before implementation
- spot contradictions across a PRD and its contracts
- save external review findings as a separate artifact
- recheck a document after selected changes
Example prompts for the agent
- Review
docs/payments.mdonce as an independent reviewer and write the findings toqa/. - Inspect
docs/api-rfc.mdwith contextp1,p2, usereviews/for output, and set modelmodel-name. - Run another review for the changed files with
--ide <ide> --reasoning <effort>.
How to install spec-peer-review
1Skills CLI (Vercel)
npx skills add pedronauck/skills --skill spec-peer-review -a claude-code2Manually: put the files in place
~/.claude/skills/spec-peer-review/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/spec-peer-review/
1Skills CLI (Vercel)
npx skills add pedronauck/skills --skill spec-peer-review -a codex2Manually: put the files in place
.agents/skills/spec-peer-review/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add pedronauck/skills --skill spec-peer-review -a cursor2Manually: put the files in place
.cursor/skills/spec-peer-review/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install pedronauck/skills skills/mine/spec-peer-review2Manually: put the files in place
.github/skills/spec-peer-review/SKILL.md1Skills CLI (Vercel)
npx skills add pedronauck/skills --skill spec-peer-review -a gemini-cli2Platform CLI
gemini skills install https://github.com/pedronauck/skills --path skills/mine/spec-peer-reviewManually: put the files in place
.devin/skills/spec-peer-review/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add pedronauck/skills --skill spec-peer-review -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about spec-peer-review
How do I install spec-peer-review in Claude Code?
Run npx skills add pedronauck/skills --skill spec-peer-review -a claude-code, then check ~/.claude/skills/spec-peer-review/SKILL.md.
What does spec-peer-review do?
It performs one independent pass over an approved planning document and produces findings for the user to accept selectively. The result is validated before the verdict is reported.
Does spec-peer-review inspect implementation code?
No. Its scope is specifications, design documents, RFCs, and detailed PRDs; implementation reviews are excluded.