What problem does it solve? Teams often jump from requirements straight to tickets without settling technology and architecture choices, causing integration failures and relitigated decisions. This Skill turns specifications, constraints, and dependency maps into an explicit technical design document with recorded architecture decisions (AD-XXX), component boundaries, data models, and interface contracts under .gener8v/technical-design/. ## Core Features & Use Cases - Architecture Decision Records: Documents each decision with context, rationale, alternatives considered, consequences, and the requirement IDs it affects. - Component and Interface Design: Defines component responsibilities, dependencies, data model entities, and input/output/error contracts so developers can build sides of a boundary independently. - NFR-Traced Risks and Infrastructure: Ties every infrastructure item and technical risk to the non-functional requirement IDs it serves or threatens, feeding directly into ticket breakdown. - Use Case: After specifying a search capability with latency NFRs, run this Skill to decide between pgvector and a dedicated vector database, record the decision as AD-002 with alternatives, and hand Ticket Breakdown a technically grounded foundation. ## Quick Start Run the technical-design skill on the search-and-retrieval capability area to produce a draft architecture design from its specification and constraints.
