create-design-proposallisted

# Design Proposal When this skill is activated, produce a `docs/DESIGN.md` file that captures the architectural design for a feature or module *before* implementation begins. The goal is to make coupling decisions, interface contracts, and testability explicit upfront. **When to use this skill vs. related ones:** - `create-spec` — defines the *what* and *why* (requirements, constraints, scope). Run it first if the problem is not yet fully specified. - `create-architecture-proposal` — defines *system-wide* architecture (bounded contexts, layering). Run it first for a new system; this skill then designs one feature *within* those boundaries. - **this skill (`create-design-proposal`)** — defines the *how* for a single feature or module: components, interfaces, coupling, and test approach. ## Clarifying Questions Before writing the design, ask the engineer the following questions. Skip any already clearly answered in the conversation. **Wait for the answers before proceeding.** 1. What exactly needs to be built? Describe the feature in one or two sentences — what problem does it solve for whom? 2. Which parts of the existing codebase must this feature integrate with or extend? 3. Are there functional constraints — required APIs, protocols, data formats, or interfaces that must be respected? 4. Are there non-functional requirements — performance targets, security requirements, scalability expectations? 5. Are there any solutions or approaches already ruled out? Why were they