Translate a Discover planning artifact into an implementation design document.
npx skills add https://github.com/jkerdels/dew-plugin --skill dew-design
Please help me install this Agent Skill. Skill: dew-design Source: https://github.com/jkerdels/dew-plugin/tree/main/skills/dew-design Command: npx skills add https://github.com/jkerdels/dew-plugin --skill dew-design
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.
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.
High-intent search queries and answers about installing and using this skill.
To translate a planning document into an implementation design, you use guided Socratic dialogue to negotiate architectural perspectives and refine data models and module interfaces. This process converts planning artifacts into a structured, implementation-ready design document for production code.
The best way to track architectural assumptions during software design is to make them explicit with validation hooks throughout a phased dialogue. This approach flags unverified dependencies and requires a validation plan before proceeding to actual implementation.
You structure module interfaces and data flow by proceeding through iterative coarse-to-fine architectural refinement. This involves evaluating at least two design alternatives at each major decision point against agreed perspectives to produce a structured auditable output.
Yes, you can evaluate alternative data models before finalizing your implementation design. The process presents at least two alternatives at each major decision point and evaluates them against prioritized design criteria to ensure trade-offs are explicitly negotiated.
An implementation design document for engineering teams should include subsystems, data flow, module interfaces, error handling, validation plan, implementation steps, and a decision log. This structured output ensures production code structure is fully defined.
alo-expGenerate SPEC.md and REQUIREMENTS.md via structured Socratic dialogue.
dmayerdesignPlan implementation from a behavioral spec into a testable design plan.
1J6K21Discover and apply the appropriate engineering skill for a given development task.
tomwangowaFacilitate Socratic design dialogue to define requirements and document approved software designs.
