What problem does it solve? Load bearing technical decisions often go unmade or undocumented, leaving builders to invent answers mid implementation. This Skill runs a structured design conversation, weighs options with a clear recommendation, and records the outcome as a numbered build spec in docs/specs/ so downstream build and verify steps work from a settled contract. ## Core Features & Use Cases - Four design modes: FEATURE for new features, ARCHITECTURE for stack selection, ENHANCEMENT for improving existing systems, and CROSS-CUTTING for codebase wide standards. - Staged discovery conversation: sorts every question into INFER, ASK, or RECOMMEND so the engineer is only asked what they alone know, with expert recommendations for everything else. - Spec lifecycle management: creates, updates, supersedes, or ratifies specs with status tracking (Proposed, In Progress, Accepted, Assumed) linked to the feature build lifecycle. - Use Case: When deciding how to add org isolation to a B2B SaaS app, run the architect skill to deliberate the data model and enforcement approach, then receive a spec with acceptance criteria, a build plan, and consequences that the develop skill builds against. ## Quick Start Run /architect with a one or two sentence description of the feature, system, or technical choice you need to design.
