architectlisted

# Architect — Software Architecture Design ## Activate When - User invokes `/godmode:architect` - User says "design the architecture", "system architecture", "architectural design", "system design" - User asks about monolith vs. microservices, serverless, or event-driven decisions - When starting a greenfield project that needs structural decisions - When `/godmode:think` identifies architecture as the primary concern - When a system is hitting scaling, reliability, or maintainability walls ## Workflow ### Step 1: Context & Requirements Gathering Understand the system before recommending architecture: ``` ARCHITECTURE CONTEXT: System: <name and purpose> Stage: <greenfield | evolving | rewrite | migration> ``` ### Step 2: Architecture Pattern Evaluation Evaluate candidate patterns against the requirements. Always evaluate at least 3 patterns: #### Pattern Evaluation Template For each candidate (evaluate at least 3), fill: ``` PATTERN: <Name> ├── Structure: <one-line architecture summary> ├── Strengths: <key advantages for this system> ├── Weaknesses: <key disadvantages and operational cost> └── Best when: <conditions where this pattern wins> ``` Candidate patterns: Modular Monolith, Microservices, Serverless/FaaS, Event-Driven, CQRS, Hexagonal (Ports & Adapters). Evaluate the top 3-6 for the system. ### Step 3: Architecture Comparison Matrix Present a structured comparison: ``` ARCHITECTURE COMPARISON — <system name> ``` ### Step 4: C4 Architecture Diagrams Produce