What problem does it solve? Design discussions often end with fuzzy terminology and decisions that live only in chat transcripts, forcing teams to re-litigate vocabulary later. This Skill runs a relentless interview that challenges ambiguous terms and contradictions while writing durable domain documentation as decisions crystallise. ## Core Features & Use Cases - Relentless design interview: Challenges fuzzy terms, surfaces contradictions with code and existing glossary entries, and forces concrete scenarios until the plan is sharp enough to implement. - Inline documentation updates: Updates the CONTEXT.md glossary and creates ADRs in docs/adr as decisions are made, plus optional living alignment docs when the repo declares them. - First-party domain-modeling integration: Loads the sibling domain-modeling skill directly, with no third-party mattpocock/skills runtime dependency. - Use Case: When starting a new feature, run the interview to pin down domain vocabulary, record architectural decisions as ADRs, and leave the repo with an accurate glossary instead of a lost chat transcript. ## Quick Start Ask the agent to grill you on your new feature design and update the project glossary and ADRs as decisions are made.
