design-review-gate

Coordinate five specialist agents to review design documents and enforce unanimous approval.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/Prekzursil/quality-zero-platform --skill design-review-gate-prekzursil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-review-gate
Source: https://github.com/Prekzursil/quality-zero-platform/tree/main/.claude/plugins/metaswarm/skills/design-review-gate
Command: npx skills add https://github.com/Prekzursil/quality-zero-platform --skill design-review-gate-prekzursil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures complex design documents receive thorough, cross-disciplinary review before implementation by coordinating Product, Architecture, Design, Security, and CTO evaluations and preventing premature development work.

Core Features & Use Cases

  • Parallel multi-agent reviews: Spawns five specialist agents (PM, Architect, Designer, Security, CTO) to review a design document in parallel and aggregate structured verdicts.
  • Iterative gating and escalation: Runs up to three revision cycles, consolidates blockers, and escalates to a human decision after repeated failures.
  • Coordination modes: Supports Task Mode for stateless, fresh reviewers and Team Mode for persistent reviewers with context retention to reduce cold starts.
  • Use Case: Use when committing docs/plans/*-design.md or after a brainstorming output to verify readiness, produce an epic, and start implementation only when all reviewers approve.

Quick Start

Trigger the design-review-gate on a design file (for example, docs/plans/user-auth-design.md) to request PM, Architect, Designer, Security, and CTO reviews and receive a consolidated approval report.

Frequently Asked Questions about design-review-gate

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

FAQPage Schema
How do I get multi-expert approval before implementation of my design document?

To get multi-expert approval before implementation, you trigger a cross-disciplinary design review that spawns five specialist agents to evaluate your design document in parallel and consolidate their structured verdicts.

What happens if my design document fails security and architecture review?

If your design document fails review, the system runs up to three iterative revision cycles to consolidate blockers, and if repeated failures occur, it escalates the final decision to a human.

Can I use fresh reviewers for each design review cycle instead of persistent context?

Yes, you can use Task Mode for stateless, fresh reviewers during each design review cycle, or switch to Team Mode for persistent reviewers with context retention to reduce cold starts.

When do I need a cross-disciplinary design review for my project plans?

You need a cross-disciplinary design review when committing design documents to docs/plans/*-design.md or after brainstorming outputs, ensuring PM, architect, designer, security, and CTO readiness before development.

Does multi-agent design review enforce unanimous approval from all specialists?

Yes, multi-agent design review enforces unanimous approval across five specialist agents, preventing premature development work until product, architecture, design, security, and CTO evaluations are all positive.

How do I coordinate Product, Architecture, Design, Security, and CTO evaluations for a plan?

You coordinate these evaluations by triggering an automated review gate on your design file, which spawns the five specialist agents in parallel to aggregate structured verdicts and produce an epic upon approval.