design-dialogue

Guides interactive design dialogue from idea to explicitly approved design summary.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough idea into a solid, approved software design often fails because proposals go unchallenged, requirements stay vague, and approval is assumed rather than explicit. This Skill structures the entire design conversation so the final design has survived real objections and carries documented user approval. ## Core Features & Use Cases - Depth-adaptive dialogue: Reads the brief to calibrate between capturing an already-settled design, grilling at full speed with an expert, or walking a newcomer through the codebase while designing. - The grill: Proposes one concrete approach anchored in the actual code, then argues the strongest case against it, routing the objection to the user or to the code depending on who can settle it. - Sectioned approval and review: Presents the design in sections (architecture, components, data flow, error handling, testing), consolidates a self-contained summary, runs a design review, and takes explicit final approval before releasing plan mode. - Use Case: A user says "I want to add structured logging across the API service." The Skill explores the affected code, asks targeted clarifying questions, pressure-tests the migration approach, and delivers an approved design summary ready for ticketing or implementation. ## Quick Start Ask the assistant to design a feature together interactively, for example: "Walk me through designing the new caching layer and push back on my proposal."

Frequently Asked Questions about design-dialogue

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

FAQPage Schema
How do I design a feature interactively with an AI assistant?

Start an interactive design dialogue by describing your idea and asking to design it together. The Skill explores the affected code, asks one clarifying question at a time, proposes and challenges an approach, then presents the design in sections for your approval.

What is the grill in a design dialogue?

The grill is a step where the assistant proposes the approach it believes is right, then argues the strongest case against it. The objection must be one that would change the design if true, and it is settled either by the user or by checking the code.

When should I not use an interactive design dialogue?

Skip it for bugs, which go through debug-investigation first, for tickets already carrying an approved design, for trivial changes below the design threshold, and when you want hands-off deliberation, which belongs to a different skill.

Does the design dialogue write files while designing?

No. The conversation is the design medium and nothing is written to disk while designing. The Skill runs in plan mode and only releases it via ExitPlanMode after you give explicit final approval of the reviewed summary.

How does the design dialogue adapt to my experience level?

It reads your brief for how settled the design is and how well you know the codebase, then states its chosen depth in one line. Depths range from capturing a settled design quickly to a full walkthrough that names and locates each codebase pattern.

What happens after the design is approved?

After explicit approval, plan mode is released carrying the approved summary, and the Skill asks what happens next: create tickets first, implement directly, or hand off to another available implementation skill. It then follows your choice.