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 work follows a settled decision. ## 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 like error handling or auth. - Structured discovery: sorts every question into INFER, ASK, or RECOMMEND, challenges weak premises against known failure patterns, and never presents a neutral menu of options. - Spec lifecycle management: creates, updates, supersedes, or ratifies specs with status tracking (Proposed, In Progress, Accepted, Assumed), umbrella directory specs for multi decision topics, and scope file linking. - Use Case: A team needs to choose between REST and GraphQL for a new API. Run /architect, answer the staged design questions, and receive a written spec with the decision, rationale, data model, acceptance criteria, and an ordered build plan. ## Quick Start Run /architect with a one sentence description of the feature, system, or technical choice you need to design.
