dev-design

Present implementation options with trade-offs and require user approval before planning.

19|5|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/edwinhu/workflows --skill dev-design-edwinhu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-design
Source: https://github.com/edwinhu/workflows/tree/main/lib/skills/dev-design
Command: npx skills add https://github.com/edwinhu/workflows --skill dev-design-edwinhu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that before any code is written, a clear, user-approved implementation plan is established, preventing wasted development effort on unvetted designs.

Core Features & Use Cases

  • Architecture Proposal: Presents 2-3 distinct implementation approaches with clear trade-offs.
  • User Approval Gate: Mandates explicit user sign-off on the chosen approach and the final plan before implementation begins.
  • Feature Decomposition: Helps break down large features into manageable, independent tasks.
  • Use Case: When tasked with adding a new authentication method, this Skill will present options like "minimal changes," "clean architecture," or a "pragmatic balance," explain the pros and cons of each, and wait for the user to select one before proceeding to detailed planning.

Quick Start

Use the dev-design skill to propose architecture approaches for the new user profile feature.

Frequently Asked Questions about dev-design

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

FAQPage Schema
How do I get explicit approval for a software architecture design before development starts?

You can get explicit architecture design approval by presenting multiple implementation approaches with clear trade-offs and mandating user sign-off on the selected plan before development begins. This enforces a structured approval gate.

What is the best way to break down a large software feature into manageable planning tasks?

The best way to break down large features is to decompose them into manageable, independent tasks during the planning phase. This ensures the architecture selection aligns with project goals before detailed implementation proceeds.

How do I compare different implementation approaches for a new feature?

You can compare implementation approaches by evaluating 2-3 distinct architecture options, such as a minimal change, clean architecture, or pragmatic balance, to understand the pros and cons of each before selection.

Do I need to choose an architecture approach before creating a detailed implementation plan?

Yes, you need to choose an architecture approach before creating a detailed implementation plan. Requiring explicit user consent on the chosen approach ensures alignment with requirements before proceeding to detailed planning.

Why should I wait for user sign-off before proceeding to software implementation?

You should wait for user sign-off to prevent wasted development effort on unvetted designs. Establishing a clear, user-approved implementation plan before code is written ensures the architecture selection meets project goals.