create-architecture-proposallisted

# Architecture Proposal When this skill is activated, produce a `docs/SYSTEM_DESIGN.md` that defines the architecture of a system *before* implementation begins. This is not a retrospective documentation — it is a forward-looking architectural blueprint that guides all subsequent design and implementation decisions. **When to use this skill vs. related ones:** - `create-spec` — defines the *what* and *why* (requirements, constraints, scope). Run it first if requirements are not yet pinned down. - **this skill (`create-architecture-proposal`)** — defines *system-wide* architecture: bounded contexts, layering, system patterns, quality attributes. Run it once per system. - `create-design-proposal` — defines the *how* for a single feature, operating *within* the boundaries this skill sets. Run it per feature, after this. ## Clarifying Questions Before writing the system design, ask the engineer the following questions. Skip any already clearly answered in the conversation. **Wait for the answers before proceeding.** 1. What is the system's primary purpose? What problem does it solve, and for whom? 2. What are the 3–5 most important use cases or workflows the system must support? 3. What quality attributes matter most — e.g. testability, scalability, availability, security, maintainability? Rank the top 3. 4. What are the technical constraints? (existing stack, required frameworks, deployment target, team expertise) 5. What is the expected scale? (approximate requests/day, da