Overview

Design Review Gate runs six specialist reviews in parallel and requires unanimous approval before implementation. If any reviewer rejects, findings are consolidated and the design is iterated up to three times before escalation.

How This Skill Works

Six reviewers (PM, Architect, Designer, Security Design, UX, CTO) assess the design in parallel. All must approve; any rejection triggers consolidation of findings and an iteration cycle, capped at three iterations before escalation.

When to Use It

• After brainstorming and planning, before implementation
• When validating a new feature design
• When introducing new architectural patterns
• For critical features requiring cross-disciplinary clearance
• During design refreshes to enforce security, UX, and architectural alignment

Quick Start

1. Step 1: Initiate six parallel reviews (PM, Architect, Designer, Security Design, UX, CTO) using the metaswarm gate
2. Step 2: Gather unanimous approvals; if any reviewer rejects, log findings and prepare an iteration plan
3. Step 3: Repeat up to three iterations; escalate to a human if still unresolved

Best Practices

• Define unanimous approval criteria up front and align reviewers' focus
• Run all six reviews in parallel to save time
• Document each review's findings and rationale
• Limit iterations to a maximum of three before escalation
• Consolidate feedback before iteration steps to avoid redundancy

Example Use Cases

• Rolling out a new payment feature with UX, security, and API implications
• Adopting a new microservice pattern across the stack
• Overhauling the user onboarding flow with usability and accessibility checks
• Rearchitecting data access for performance while maintaining security
• Assessing a critical risk feature requiring unanimous sign-off before launch

Frequently Asked Questions