dew-design

What problem does it solve?

It converts a prior planning or “Discover” artifact into a concrete, implementation-ready architecture by guiding a careful, Socratic design dialogue that makes assumptions explicit and negotiates trade-offs.

Core Features & Use Cases

• Socratic, phased design exploration: Summarizes the planning document, negotiates design perspectives, then proceeds through coarse architecture, data modeling, module interfaces, and detail refinement.
• Alternatives with explicit trade-offs: Presents at least two alternatives at each major decision point and evaluates them against the agreed design perspectives.
• Assumptions made explicit with validation hooks: Flags unverified dependencies and requires a validation plan before implementation.
• Auditable output: Produces a structured Implementation Design Document including subsystems, data flow, interfaces, error handling, validation, implementation order, and a decision log.

Quick Start

Use the dew-design skill to transform your Discover output into an implementation design by answering one design question at a time and choosing between the proposed alternatives.