brainstorming-extension

Enforce a five-reviewer design gate on committed design documents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces a mandatory design review gate when a design document is committed after brainstorming, preventing unreviewed designs from progressing directly to planning and implementation.

Core Features & Use Cases

  • Mandatory 5-agent review: Spawns Product Manager, Architect, Designer, Security Design, and CTO reviewers and requires approval from all five before proceeding.
  • Iteration and escalation: Allows up to three revision cycles for designs flagged as needs_revision and escalates to a human decision if issues persist.
  • Pipeline integration: Detects design document commits from the brainstorming flow and blocks transition to writing-plans until the gate is passed; supports explicit skip with confirmation for trivial changes.
  • Use Case: When brainstorming commits a new architecture doc, run this gate to catch architectural, security, UX, and requirements issues before implementation begins.

Quick Start

Ask the skill to run the design-review-gate on the committed design document path to enforce the 5-agent review.

Frequently Asked Questions about brainstorming-extension

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

FAQPage Schema
How do I enforce a mandatory design review gate after brainstorming commits?

To enforce a mandatory design review gate after brainstorming commits, this skill blocks unreviewed design documents from progressing to writing-plans by running five parallel reviewers for architecture, security, UX, and requirements validation.

What is a multi-agent design review workflow for design documents?

A multi-agent design review workflow spawns five parallel reviewers—Product Manager, Architect, Designer, Security, and CTO—to validate architecture, security, UX, and requirements before allowing a design document to proceed to implementation.

How do I handle revision cycles when a design review gate fails?

When a design review gate fails, the workflow allows up to three iteration cycles for designs flagged as needing revision, escalating to a human decision if issues persist after repeated failures.

Can I skip the design review gate for trivial changes?

Yes, you can skip the design review gate for trivial changes by providing a confirmed skip, bypassing the five parallel reviewers and allowing the design document to transition to writing-plans.

Does the 5-agent review process block the transition to writing-plans?

Yes, the 5-agent review process blocks the transition to writing-plans until the gate is passed, requiring approval from all five reviewers before the committed design document can progress.

What are the limitations of automated multi-agent design review gates?

Limitations of automated multi-agent design review gates include a maximum of three revision cycles before human escalation is required, and the need for explicit confirmation to skip reviews for trivial changes.