What problem does it solve?
Adversarial interview against the documented domain. Walk every branch of the design; resolve dependencies one decision at a time; recommend an answer per question. Ask one question per turn — wait for response before continuing.
When a term is answerable from the codebase, dispatch an Explore agent for first discovery rather than asking. The user is the source of intent; the codebase is the source of fact.
Modality vs adjacent skills: This is adversarial-relentless interview against documented domain language. Clarifying-question protocol is VS-shaped (hypothesis sampling + clarifying questions). General adversarial interview is general-purpose without domain-language anchor. Pick this skill when the project has or needs CONTEXT.md and ADRs as the artifact under stress-test.
Core Features & Use Cases
- Adversarial glossary stress-test against CONTEXT.md and ADRs to surface ambiguous terms and conflicts.
- Canonical-term proposals when terminology is overloaded or ambiguous, with clear alternatives.
- Inline glossary updates to CONTEXT.md and ADRs when meaningful trade-offs are observed.
Quick Start
Run an adversarial-domain-interview against the current CONTEXT.md and ADRs to surface terminology gaps and update the glossary accordingly.