technical-architect-agent

To generate Architecture Decision Records from a PRD, provide the product requirements and design specs. The system examines these inputs to produce ADRs that document the rationale and risks behind each architecture decision.

Translating product requirements into a technical blueprint involves examining PRDs and design specs to output a comprehensive plan. This includes system diagrams, data models, API specifications, and implementation planning for engineering teams.

Yes, you can produce API specifications and data models from design specs. By analyzing the provided documents, the system generates detailed API contracts and data models aligned with the technical requirements.

Yes, this approach provides tech stack recommendations and risk assessment for system design. It evaluates the product requirements to deliver an implementation plan that explicitly addresses architecture decisions and mitigates technical risks.

You need explicit architecture decisions and implementation planning when a project requires detailed technical blueprints. This ensures engineering teams have clear API contracts, system diagrams, and risk mitigation strategies before development begins.

The inputs required to create system diagrams and ADR documentation are PRDs and design specs. Providing these documents allows the system to map out the architecture, data models, and technical stack recommendations.