design-committee

Deliberates design decisions through three lens agents, cross-examination, and evidence-based synthesis.

3|3|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/philipobenito/elelem --skill design-committee-philipobenito
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-committee
Source: https://github.com/philipobenito/elelem/tree/main/skills/design-committee
Command: npx skills add https://github.com/philipobenito/elelem --skill design-committee-philipobenito

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Making non-trivial design decisions alone risks blind spots, and asking the user every design question defeats the purpose of delegating. This Skill runs a hands-off deliberation where three lens agents (Pragmatist, Architect, Advocate) independently position, cross-examine each other, and a synthesiser resolves each decision on cited evidence, returning an approved design without user involvement until the end. ## Core Features & Use Cases - Multi-lens deliberation: Three agents with distinct failure-mode briefs state independent positions concurrently, then cross-examine each other, with vote counting explicitly forbidden in synthesis. - Structured resolution pipeline: A workflow script runs decision groups sequentially, carries consensus forward, applies one tiebreak per split decision, and returns genuinely unresolved decisions to the user. - Review and approval gate: The consolidated design summary goes through a design review, targeted re-deliberation rounds for contested changes, and explicit user approval before implementation. - Use Case: A user says "Add webhook delivery for order events, come back when you have a design." The Skill confirms the brief, explores the codebase, deliberates delivery mechanism and retry semantics across the lenses, resolves the decisions, and presents a reviewed design for approval. ## Quick Start Ask the agent to design a feature hands-off using the design committee, for example: "Design the webhook delivery system for order events, don't ask me design questions, come back when it's done."

Frequently Asked Questions about design-committee

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

FAQPage Schema
How do I get an AI to make design decisions without asking me questions?

Use a hands-off design deliberation where three lens agents (Pragmatist, Architect, Advocate) state independent positions, cross-examine each other, and a synthesiser resolves each decision on cited evidence. You confirm the brief once, then see nothing until the finished design is presented for approval.

How does multi-agent design deliberation avoid groupthink?

Each lens agent is briefed to catch a different failure mode, and the synthesis brief forbids resolving decisions by counting agreement, since correlated agents agreeing is not evidence. Decisions are weighed on cited files and named failure modes, with a lone dissent backed by code outranking ungrounded majority agreement.

When should I not use a design committee workflow?

Avoid it when the work holds fewer than two meaningful design decisions, since deliberating one settled question produces theatre rather than a design. In that case use an interactive design dialogue instead. Being hands-off must also be explicitly requested by the user, never inferred.

What happens when the deliberating agents cannot agree on a decision?

A decision still split after synthesis gets exactly one tiebreak round from a fresh adjudicator. If it remains split, it is recorded as unresolved and presented to the user with the competing positions and their evidence, since it genuinely belongs to a human.

What tools does the design committee skill require to run?

It requires plan mode and the Workflow tool to run the shipped design-workflow.js script. If Workflow is unavailable, the same rounds can run sequentially through one-shot Agent dispatches; if Agent is also unavailable, the skill stops and recommends the interactive dialogue.