architect

To generate a technical architecture document, you apply an architecture skill to an existing product spec to produce a comprehensive architecture file. This document defines the technology stack, system design, API contracts, database schemas, and observability strategy for the entire project.

The best way to define a technology stack and system design is by interactively cataloging foundational decisions with their trade-offs and recommended choices. This collaborative resolution ensures every technology choice aligns explicitly with the product spec before generating execution plans.

A comprehensive technical architecture deliverable includes technology stack tables, system diagrams, directory structure, configuration examples, API routes, database schemas, pipeline flows, and an observability strategy. It consolidates all foundational design work into a single guiding document.

Yes, you need a product spec before defining technical architecture and API contracts. The architecture generation process requires reading an existing product spec file to ensure every foundational technology choice and schema design aligns directly with the specified product requirements.

To resolve technology trade-offs when creating a system design, you use interactive user consultation grouped into decision rounds. This process enumerates options for web frameworks and data storage, maps open questions, and produces a key decisions summary for the project.

You need a project-level architecture document for pipeline orchestration after ideation produces a product spec and before generating plan-level architectures. It locks down project-wide design, avoiding ad-hoc or duplicated design work across multiple execution plans.