What problem does it solve? Engineers often jump into code before a design is fully understood, leading to vague entities, missing contracts, and conflicting requirements. This Skill acts as a thinking partner that pressure-tests your architecture, requirements, and tradeoffs before implementation begins. ## Core Features & Use Cases - Design Model Building: Structures your thinking across conceptual, runtime, storage, contract, and operational models. - Decision Recording: Captures decisions with context, consequences, rejected alternatives, and reversibility in an ADR-style format. - Risk Surfacing: Identifies duplicated sources of truth, unclear ownership, migration issues, and observability gaps. - Use Case: You are designing a new notification service and are unsure where retry state should live. Use this Skill to clarify core entities, define ownership boundaries, and record the tradeoffs before writing any code. ## Quick Start Ask the assistant to act as a design partner and review your proposed architecture for a new service, focusing on core entities, contracts, and risks.
