Technical Architecture
Create a technical architecture plan for a new or evolving system from its requirements. Ranks quality attributes with measurable targets, sizes load and storage with back-of-envelope capacity math, sets system boundaries and data ownership, maps the context, containers, and data flows for key scenarios, designs APIs and data storage by access pattern, covers infrastructure, security trust boundaries, and failure modes, and records each major choice as a decision with options, criteria, reversibility, and a build sequence that proves the riskiest assumptions first. Use when someone asks to design a system architecture, choose between a monolith and services, plan data flow and APIs, size infrastructure, or document architecture decisions and tradeoffs. Do not use for splitting a finished design into tickets (use technical-requirements-splitter), assessing an existing codebase (use codebase-audit), planning a move between systems (use migration-plan), or writing infrastructure definitions (use iac-setup).