System Architect

Design system architecture by mapping functional and non-functional requirements to components, interfaces, and patterns. This approach translates PRD or tech-spec inputs into structured architecture blueprints, capturing decision rationales and trade-offs for reliable scale and maintainability.

Document architecture decisions and trade-offs by generating decision logs, architecture diagrams, and API specs. This ensures that pattern selections, such as microservices or modular monoliths, are captured and traceable within your project workflow.

Choose between a modular monolith and microservices by evaluating trade-offs against your specific FRs and NFRs. This process selects appropriate architectural patterns with justification, ensuring the chosen structure satisfies your project's scale and maintainability requirements.

Yes, you need a PRD or tech-spec to generate a complete system architecture blueprint. Providing these requirement documents as input allows the architecture workflow to map functional and non-functional needs to robust system designs and documentation.

Produce architectural artifacts like architecture diagrams, decision logs, and API specs for new products requiring reliable scale. These outputs map FRs and NFRs to concrete components and integration points, loading directly into the project workflow for implementation.