domain-model

Stress-test domain terminology in CONTEXT.md and ADRs to surface canonical terms.

5|2|Updated Nov 17, 2025
One-click install
npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill domain-model-outlinedriven
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain-model
Source: https://github.com/OutlineDriven/odin-gemini-cli-extension/tree/main/skills/domain-model
Command: npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill domain-model-outlinedriven

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about domain-model

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stress-test domain language in CONTEXT.md for ambiguous terminology?

Stress-test domain language by running an adversarial interview against CONTEXT.md to identify ambiguous terms, surface conflicts, and propose canonical terminology updates inline.

What is the best way to resolve terminology conflicts across multiple project contexts?

Resolve terminology conflicts by applying a stress-test workflow across multi-context setups to surface dependencies and align domain language with project reality.

When do I need to create an ADR for domain model decisions?

Create an ADR for domain model decisions when meaningful trade-offs are observed during the adversarial interview and require formal documentation alongside CONTEXT.md updates.

Can I use an adversarial interview to check if documented glossary terms match the codebase?

Yes, an adversarial interview dispatches an Explore agent to verify documented glossary terms against codebase facts, using the user only as the source of intent.

How does adversarial domain interviewing compare to general clarifying question protocols?

Adversarial domain interviewing anchors specifically to documented domain language in CONTEXT.md and ADRs, whereas general protocols sample hypotheses without domain-language anchors.

What are the limitations of relying on adversarial interviews for domain language alignment?

Adversarial interviews focus strictly on documented domain language artifacts and resolve decisions one question per turn, requiring existing or planned CONTEXT.md and ADR files to function effectively.