create-architecture

Architecture documentation translates requirements into technical design by extracting functional and non-functional needs, selecting patterns, and producing comprehensive docs with Architecture Decision Records (ADRs) that justify technology choices and deployment approach for stakeholder review.

Architecture documents must cover deployment design, security considerations, technology stack justification with trade-offs, multi-region deployment patterns, and governance artifacts. ADRs provide rationale for each architectural decision affecting system reliability and compliance.

Yes, architecture generation adapts to project type and complexity. The process handles Frontend, Backend, and Fullstack architectures by determining project scope, applying appropriate patterns, and scaling documentation depth based on system requirements and brownfield context.

ADRs document the rationale, alternatives considered, and consequences of architectural choices. They create traceability between requirements and design decisions, enabling teams to understand why specific technology stacks and patterns were selected for particular project contexts.

Begin with requirements analysis to extract functional and non-functional specifications, then provide project context including type, complexity, and existing brownfield systems. This enables accurate technology stack selection and deployment design tailored to your specific constraints.

Create architecture documentation when transitioning from product requirements or epics to technical implementation. It's essential before development begins for Frontend, Backend, or Fullstack projects to ensure stakeholder alignment on design decisions and deployment strategy.