bmild-roundtable

Orchestrate multi-persona deliberations to surface trade-offs in design decisions.

3|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/micfre/BMILD --skill bmild-roundtable
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmild-roundtable
Source: https://github.com/micfre/BMILD/tree/main/.agents/skills/bmild-roundtable
Command: npx skills add https://github.com/micfre/BMILD --skill bmild-roundtable

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of getting structured, cross-functional input on complex design and specification decisions without manual coordination of multiple stakeholders, reducing the risk of expensive downstream rework from unvetted, under-discussed choices.

Core Features & Use Cases

  • Configurable Multi-Persona Deliberation: Convene any subset of BMILD's design-tier personas (Product, UX, Architect, QA, Security) tailored to your question's domain.
  • Structured Diverge-Converge Flow: Enforces genuine discussion of trade-offs instead of diplomatic consensus, surfacing real tensions between competing valid perspectives.
  • Dual Context Support: Works for both forward-direction design work and course-correction consultations, returning synthesis to the right owner automatically.
  • Use Case: When designing a new user authentication flow, convene a roundtable with your Product, UX, Architect, and Security personas to surface trade-offs between user experience, technical feasibility, and security constraints before committing to a direction.

Quick Start

Invoke the bmild-roundtable skill with your complex design or specification question, confirm the proposed attendees, and follow the facilitated deliberation to surface clear trade-offs for your decision.

Frequently Asked Questions about bmild-roundtable

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

FAQPage Schema
How do I surface cross-functional trade-offs for complex design decisions?

Structured multi-persona deliberation surfaces cross-functional trade-offs for complex design decisions by convening configurable design-tier personas. This enforces genuine discussion of trade-offs instead of diplomatic consensus, exposing real tensions between competing valid perspectives.

What is the best way to resolve consequential ambiguity in spec-driven development?

Structured multi-persona deliberation resolves consequential ambiguity in spec-driven development by surfacing cross-functional trade-offs. This mitigates the risk of expensive downstream rework from unvetted or under-discussed choices by returning trade-off records for user ratification.

Can I configure which personas attend a design deliberation session?

You can configure attendance for a design deliberation session by convening any subset of design-tier personas, such as Product, UX, Architect, QA, and Security. This allows you to tailor the cross-functional input specifically to your question's domain.

Does this deliberation approach provide a final recommendation for design choices?

This deliberation approach enforces a no-recommendation synthesis rule for design choices. Instead of providing a final recommendation, it returns structured trade-off records to the invoking persona or change proposal artifact for explicit user ratification.

When do I need a multi-persona roundtable for design and specification decisions?

You need a multi-persona roundtable for design and specification decisions when competing defensible answers risk expensive downstream rework. It supports both forward-direction design sessions and course-correction consultations by surfacing trade-offs for user ratification.

Why does multi-persona deliberation avoid diplomatic consensus during design discussions?

Multi-persona deliberation avoids diplomatic consensus to ensure genuine discussion of trade-offs. By enforcing a structured diverge-converge flow, it surfaces real tensions between competing valid perspectives rather than masking them with superficial agreement.