Architecture Planning

Edge Cases

Workflow

flowchart TD
    A([Start: Architecture Planning]) --> B{scale_requirements\nprovided and consistent?}
    B -- Missing/Vague --> C[Ask for clarification:\nDAU, uptime, latency targets]
    C --> B
    B -- Yes --> D{tech_stack conflicts\nwith scale requirements?}
    D -- Yes --> E[Flag mismatch explicitly\nrecommend compatible alternative]
    D -- No --> F{tech_stack open-ended?}
    F -- Yes --> G[Recommend specific stack\nwith rationale\nask developer to confirm]
    F -- No --> H[List Component Overview\nname + responsibility + tech + interfaces]
    G --> H
    H --> I{Monolith or\ndistributed?}
    I -- Ambiguous --> J[Default to monolith\nfor given scale\nnote extraction path]
    I -- Clear --> K[Describe Data Flow\nfor 2 critical user journeys\nsync vs async explicit]
    J --> K
    K --> L[Write Technology Decisions\nwith rationale + rejected alternatives\n+ trade-offs accepted]
    L --> M[Write Scalability Considerations\nhorizontal/vertical per component\nbottleneck identification + caching]
    M --> N[Produce ASCII Architecture Diagram\ncomponents + connections\nlabeled with protocol/data type]
    N --> O([Output: 5-section architecture plan\n600–1200 words])

Examples

• Input Example
• Output Example

Quality Gate

• Components have clear boundaries.
• Data flows cover critical paths.
• Tech choices are justified.
• Scalability strategy is quantified.
• Diagram included.

Changelog