design-discussion

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.