Agent skill · writing content · pedronauck
spec-peer-review
Run one requested external review of an approved spec, design doc, RFC, or detailed PRD; produce findings for user-selected incorporation. Excludes implementation reviews and automatic or looping approval gates.
Why this skill is useful
Adds a structured peer review process for specifications that incorporates domain-specific knowledge and validation scripts not commonly found in public documentation.
What it needs
Requires compozy installed locally. About 2k tokens when loaded. Last updated 2026-08-01. 564 stars on the source repository.
What this skill does
Spec Peer Review Review a saved design only when the user requests an independent review. Honor existing approval to review it as-is. Incorporate only selected findings; additional rounds remain opt-in. Inputs and output Resolve the spec from the request or active context. Ask only when ambiguous. Accept additional context and an output directory. Default to the spec's qa/ directory for .compozy/tasks/<slug>/, otherwise .peer-reviews/<UTC-timestamp>/. Use the configured reviewer runtime/model and reasoning. Explicit overrides win; never pin a historical model or silently replace a user-selected model. Keep one findings artifact per round: <out>/peer-review-findings-roundN.md. Preserve prior rounds. Review 1. Read the spec and its linked contract index. Include relevant requirements, concrete examples, test contracts, ADR decisions, and the instructions for affected surfaces. Expand into other context when a dependency or contradiction needs it; do not load every memory file. 2. Use the applicable markers in references/quality-markers.md; missing contracts become findings, not an automatic stop before a requested review. 3. Read references/peer-review-prompt.md and fill its placeholders, including exact findings path, round, resolved runtime/model, and context paths. The reviewer may write only that findings file. 4. Launch through the available independent reviewer runtime (a configured native reviewer, Compozy session, or herdr TUI). Use that runtime's documented commands; do not assume a retired compozy exec API. Preserve existing worker identity for follow-up rounds when available. 5. Inspect the findings, cited evidence, and changed paths. Validate the artifact: 6. Report the verdict, material findings, limitations, and artifact path. Missing/malformed output is an incomplete review, never READY. Repair an operational failure within the authorized round; do not start additional substantive rounds automatically. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills pedronauck/spec-peer-review