design-discussion

Orchestrates expert teams to compare architectures and produce ADR-based decisions.

35|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/sean-sunagaku/claude-code-plugin --skill design-discussion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-discussion
Source: https://github.com/sean-sunagaku/claude-code-plugin/tree/main/design-discussion/skills/design-discussion
Command: npx skills add https://github.com/sean-sunagaku/claude-code-plugin --skill design-discussion

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps engineering and product teams collaborate on complex technical decisions by orchestrating a five-strong expert agent cohort to analyze, compare, and decide on design approaches. It provides structured workflows, ADR-style decisions, and traceable logs to reduce ambiguity and risk in architectural choices.

Core Features & Use Cases

  • Structured debate framework: Facilitates a formal, multi-round discussion with dedicated roles (facilitator, solution architect, engineer, product manager, user liaison, and devil's advocate).
  • Comparative design analysis: Generates 2-4 concrete design proposals, evaluates them on technical feasibility, cost, maintainability, and business value, and surfaces risks.
  • ADR and action planning: Produces Architecture Decision Records and concrete implementation tasks with traceable decisions and justifications.
  • User-aligned outcomes: Includes user approvals and questions management to ensure alignment with user needs and constraints.

Quick Start

Start a design-wall session by loading domain documents, forming the design discussion team, and beginning with Step 1: clarify the problem, constraints, and success criteria.

Ensure you read the domain docs under docs/ or .claude/ for relevant patterns and constraints before starting.

Frequently Asked Questions about design-discussion

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

FAQPage Schema
How do I facilitate a structured architectural trade-off analysis for complex technical decisions?

Architectural trade-off analysis is facilitated by coordinating a multi-agent expert team that generates 2-4 design proposals, evaluates them on feasibility and cost, and produces ADR-driven decisions with traceable logs.

What is the best way to create Architecture Decision Records for API design patterns?

Creating Architecture Decision Records for API design patterns requires a structured debate framework where expert agents evaluate technical feasibility, surface risks, and log decisions to ensure traceability and reproducibility.

Can I use a multi-agent debate format to compare database design options?

Yes, a multi-agent debate format compares database design options by assigning roles like solution architect and devil's advocate to objectively evaluate proposals, assess risks, and align outcomes with business value.

How do I start an ADR-driven decision session for tool selection?

Start an ADR-driven decision session by loading relevant domain documents, forming the expert agent cohort, and clarifying the problem, constraints, and success criteria to ensure objective evaluation.

When do I need a structured design discussion framework for architectural choices?

A structured design discussion framework is needed when architectural choices involve complex trade-offs, requiring objective evidence-based comparisons, explicit risk assessment, and user-aligned action planning to reduce ambiguity.

Does this multi-agent approach work for evaluating maintainability and business value in software architecture?

Yes, the multi-agent approach evaluates maintainability and business value by having a product manager and user liaison role within the cohort assess design proposals against technical and business constraints.