What problem does it solve? Design discussions often lose agreed terminology and hard-to-reverse decisions once the conversation ends. This Skill conducts a rigorous round-based design interview while persisting the agreed domain model into repo-local documents, so glossaries and architectural decisions survive as CONTEXT.md and docs/adr entries. ## Core Features & Use Cases - Round-based frontier interviewing: Groups independent questions into numbered rounds with recommended answers, recomputing the frontier after each reply and challenging vague or contradictory responses. - Inline glossary growth: Detects conflicts between user wording and existing CONTEXT.md definitions, proposes canonical terms, and updates the glossary immediately following CONTEXT-FORMAT.md. - Sparing ADR proposals: Suggests an ADR only when a decision is hard to reverse, surprising without context, and the result of a real trade-off, formatted per ADR-FORMAT.md. - Use Case: While designing an order domain, you mention "cancel" meaning both full cancellation and partial return. The Skill flags the ambiguity, proposes canonical terms, updates CONTEXT.md, and later drafts an ADR when you choose event sourcing for the write model. ## Quick Start Ask the agent to grill your design with docs so the agreed terms go into CONTEXT.md and the key decisions into ADRs.
