architecture-proposallisted

# Architecture Proposal When this skill is activated, produce a `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. ## 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, data volume, number of engineers maintaining it) 6. Are there any architectural patterns already decided upon or explicitly ruled out? 7. What is the biggest unknown or risk in this system right now — what keeps you up at night architecturally? 8. Is this greenfield, or does an existing codebase need to be evolved toward this design? ## Steps 1. Use the answers above as the primary input; supplement with codebase exploration if an existing system was mentioned 2. Identify the major domains and bounded contexts 3