multi-agent-brainstorming
Use this skill when a design or idea requires higher confidence, risk reduction, or formal review. This skill orchestrates a structured, sequential multi-agent design review where each agent has a strict, non-overlapping role. It prevents blind spots, false confidence, and premature convergence.
What this skill does
# Multi-Agent Brainstorming (Structured Design Review) ## Purpose Transform a single-agent design into a **robust, review-validated design** by simulating a formal peer-review process using multiple constrained agents. This skill exists to: - surface hidden assumptions - identify failure modes early - validate non-functional constraints - stress-test designs before implementation - prevent idea swarm chaos This is **not parallel brainstorming**. It is **sequential design review with enforced roles**. --- ## Operating Model - One agent designs. - Other agents review. - No agent may exceed its mandate. - Creativity is centralized; critique is distributed. - Decisions are explicit and logged. The process is **gated** and **terminates by design**. --- ## Agent Roles (Non-Negotiable) Each agent operates under a **hard scope limit**. ### 1️⃣ Primary Designer (Lead Agent) **Role:** - Owns the design - Runs the standard `brainstorming` skill - Maintains the Decision Log **May:** - Ask clarification questions - Propose designs and alternatives - Revise designs based on feedback **May NOT:** - Self-approve the final design - Ignore reviewer objections - Invent requirements post-lock --- ### 2️⃣ Skeptic / Challenger Agent **Role:** - Assume the design will fail - Identify weaknesses and risks **May:** - Question assumptions - Identify edge cases - Highlight ambiguity or overconfidence - Flag YAGNI violations **May NOT:** - Propose new features - Redesign the system - Offer alternative architectures Prompting guidance: > “Assume this design fails in production. Why?” --- ### 3️⃣ Constraint Guardian Agent **Role:** - Enforce non-functional and real-world constraints Focus areas: - performance - scalability - reliability - security & privacy - maintainability - operational cost **May:** - Reject designs that violate constraints - Request clarification of limits **May NOT:** - Debate product goals - Suggest feature changes - Optimize beyond stated requirements --- ### 4️⃣ User Advocate Agent **Role:** - Represent the end user Focus areas: - cognitive load - usability - clarity of flows - error handling from user perspective - mismatch between intent and experience **May:** - Identify confusing or misleading aspects - Flag poor defaults or unclear behavior **May NOT:** - Redesign architecture - Add features - Override stated user goals --- ### 5️⃣ Integrator / Arbiter Agent **Role:** - Resolve conflicts - Finalize decisions - Enforce exit criteria **May:** - Accept or reject objections - Require design revisions - Declare the design complete **May NOT:** - Invent new ideas - Add requirements - Reopen locked decisions without cause --- ## The Process ### Phase 1 — Single-Agent Design 1. Primary Designer runs the **standard `brainstorming` skill** 2. Understanding Lock is completed and confirmed 3. Initial design is produced 4. Decision Log is started No other agents participate yet. --- ### Phase 2 — Structured Review Loop Agents are invoked **one at a time**, in the following order: 1. Skeptic / Challenger 2. Constraint Guardian 3. User Advocate For each reviewer: - Feedback must be explicit and scoped - Objections must reference assumptions or decisions - No new features may be introduced Primary Designer must: - Respond to each objection - Revise the design if required - Update the Decision Log --- ### Phase 3 — Integration & Arbitration The Integrator / Arbiter reviews: - the final design - the Decision Log - unresolved objections The Arbiter must explicitly decide: - which objections are accepted - which are rejected (with rationale) --- ## Decision Log (Mandatory Artifact) The Decision Log must record: - Decision made - Alternatives considered - Objections raised - Resolution and rationale No design is considered valid without a completed log. --- ## Exit Criteria (Hard Stop) You may exit multi-agent brainstorming **only when all are true**: - Understanding Lock was completed - All reviewer agents have been invoked - All objections are resolved or explicitly rejected - Decision Log is complete - Arbiter has declared the design acceptable - If any criterion is unmet: - Continue review - Do NOT proceed to implementation If this skill was invoked by a routing or orchestration layer, you MUST report the final disposition explicitly as one of: APPROVED, REVISE, or REJECT, with a brief rationale. --- ## Failure Modes This Skill Prevents - Idea swarm chaos - Hallucinated consensus - Overconfident single-agent designs - Hidden assumptions - Premature implementation - Endless debate --- ## Key Principles - One designer, many reviewers - Creativity is centralized - Critique is constrained - Decisions are explicit - Process must terminate --- ## Final Reminder This skill exists to answer one question with confidence: > “If this design fails, did we do everything reasonable to catch it early?” If the answer is unclear, **do not exit this skill**.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.