multi-agent-brainstorming

Simulate structured peer review with specialized agents to validate designs.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/shimseonjo/lectuer_factory --skill multi-agent-brainstorming-shimseonjo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-agent-brainstorming
Source: https://github.com/shimseonjo/lectuer_factory/tree/main/.claude/skills/multi-agent-brainstorming
Command: npx skills add https://github.com/shimseonjo/lectuer_factory --skill multi-agent-brainstorming-shimseonjo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the risk of overconfident, single-agent designs by simulating a structured peer-review process with specialized agents to identify flaws before implementation.

Core Features & Use Cases

  • Simulated Peer Review: Employs distinct agent roles (Designer, Skeptic, Guardian, Advocate, Arbiter) to rigorously critique a design.
  • Constraint Enforcement: Ensures designs adhere to non-functional requirements and real-world limitations.
  • Decision Logging: Maintains a detailed log of all decisions, objections, and resolutions.
  • Use Case: Before launching a new feature, use this skill to have a 'Skeptic' agent challenge assumptions, a 'Constraint Guardian' check for performance issues, and a 'User Advocate' ensure usability, leading to a more robust final design.

Quick Start

Initiate a multi-agent design review for the proposed 'user-authentication-flow.md' document.

Frequently Asked Questions about multi-agent-brainstorming

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

FAQPage Schema
How do I validate a system design before implementation?

To validate a system design before implementation, you can simulate a structured peer review using multiple specialized agents to surface hidden assumptions and identify failure modes. This enforces strict agent roles and a gated review process with a mandatory decision log.

What is multi-agent peer review for design validation?

Multi-agent peer review is a process where specialized agents like a Skeptic, Guardian, and Advocate rigorously critique a design. It surfaces hidden assumptions and identifies failure modes by enforcing strict roles and a sequential, gated review process.

How do I identify failure modes in a proposed system architecture?

You identify failure modes by running a proposed architecture through a simulated peer review with specialized agents. A Skeptic agent challenges assumptions while a Constraint Guardian checks for performance issues and real-world limitations.

Can I use AI agents to check my design for non-functional requirement constraints?

Yes, you can use AI agents to check design constraints by assigning a Guardian agent to enforce non-functional requirements and real-world limitations. This ensures your architecture adheres to strict constraints during a gated review process.

What is the best way to document design decisions and objections during a review?

The best way to document design decisions and objections is to enforce a mandatory decision log during a sequential peer review. This maintains a detailed record of all decisions, objections, and resolutions generated by the specialized agents.

When should I use a multi-agent approach instead of a standard design review?

You should use a multi-agent approach when you need to mitigate the risk of overconfident, single-agent designs. It provides rigorous critique by simulating distinct roles like Designer, Skeptic, and Arbiter to validate designs before implementation.