spec-review

Orchestrate a three-phase multi-agent spec review with self-critique and cross-review.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/pamelia/opencode-plugins --skill spec-review-pamelia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-review
Source: https://github.com/pamelia/opencode-plugins/tree/main/skills/spec-review
Command: npx skills add https://github.com/pamelia/opencode-plugins --skill spec-review-pamelia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates a multi-agent, three-phase spec review to validate, challenge, and harden a spec before implementation.

Core Features & Use Cases

  • Phase-based agent selection and orchestration to ensure coverage across risk areas.
  • Self-critique and cross-agent challenges to surface and resolve disagreements.
  • Structured synthesis and final verdict with deduplication and traceability.

Quick Start

Spawn an agent team and run a three-phase spec review to produce the final assessment.

Frequently Asked Questions about spec-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate multi-agent spec review for architectural blueprints?

Automate multi-agent spec review by orchestrating a three-phase process with self-critique and cross-agent challenges to validate and harden architectural blueprints. The orchestration uses risk-based agent selection to ensure coverage across critical risk areas before producing a final structured assessment.

What is cross-review routing in spec validation?

Cross-review routing in spec validation is an agent orchestration mechanism where expert agents challenge each other's assessments to surface and resolve disagreements. It ensures design documents or API specs are thoroughly hardened through structured cross-agent challenges before final synthesis.

Can I use review automation for large or complex API specs?

Yes, review automation handles large or complex API specs by applying risk-based agent selection and phase-based orchestration. This approach ensures comprehensive coverage across risk areas, validating the spec through self-critique and cross-review to produce a structured synthesis with a final verdict.

What's the best way to track risks during a phased design document review?

Track risks during a phased design document review by orchestrating a multi-agent team with risk-based selection. The three-phase process validates the spec through self-critique and cross-review, deduplicating findings and maintaining traceability to produce a final verdict with structured synthesis.

When do I need a structured synthesis output for spec review?

You need a structured synthesis output for spec review when validating complex design documents or API specs through multi-agent orchestration. It deduplicates findings, maintains traceability across self-critique and cross-review phases, and delivers a final verdict to solidify the spec before implementation.

Does spec review orchestration work without external dependencies?

Yes, spec review orchestration works without external dependencies, relying entirely on its internal multi-agent design to execute the three-phase review. It spawns an agent team to handle self-critique, cross-agent challenges, and structured synthesis autonomously to harden the provided spec.