What problem does it solve? It turns an approved task_spec into a concrete technical architecture document, so implementation starts from justified decisions about components, data models, interfaces, and stack instead of ad-hoc choices made during coding. ## Core Features & Use Cases - Architecture Document Generation: Produces a structured architecture artifact covering functional and system architecture, data model, interfaces, technology stack, analytics events, security, reliability, and deployment. - Simplicity Enforcement: Requires every component and technology to be justified by a specific task_spec requirement, flagging unjustified complexity as premature design. - Existing-System Awareness: For enhancement work, studies prior architecture documents and code first, and raises open questions to the owner instead of silently refactoring. - Use Case: After a game slice's task_spec passes handoff review, use this Skill to produce the architecture document, then route it through the architecture-review gate before task planning begins. ## Quick Start Use the architecture-design skill to design the technical architecture for the current slice based on its approved task_spec.
