skills.rest
AgentiveStack
AgentiveStackOFFICIAL
Explore all skills by this author →
WebsiteGitHub

domain

Plan domain model stress tests and update CONTEXT.md, UBIQUITOUS_LANGUAGE.md, and ADRs.

71|17|Updated Apr 24, 2026
Search Tags:#documentation#adr#code-review#ubiquitous-language#stress-test#domain-model#context-map
One-click install
npx skills add https://github.com/AgentiveStack/skills --skill domain-agentivestack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: domain
Source: https://github.com/AgentiveStack/skills/tree/main/domain
Command: npx skills add https://github.com/AgentiveStack/skills --skill domain-agentivestack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cook a plan against the project's domain model to stress-test terminology, surface contradictions with code, and inline-update CONTEXT.md, UBIQUITOUS_LANGUAGE.md, and ADRs as decisions crystallize.

Core Features & Use Cases

  • Cross-check domain invariants and ownership across contexts.
  • Surface contradictions between decisions and code, and update documentation inline as decisions crystallize.
  • Use when planning a feature, refactoring, or any work touching domain boundaries to maintain a coherent ubiquitous language and contract surfaces.

Quick Start

Ask the AI to cook a domain stress-test plan for the feature you are planning.

Frequently Asked Questions about domain

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

FAQPage Schema
How do I stress-test a domain model for terminology conflicts?▼

To stress-test a domain model, you cross-check invariants and ownership across contexts to surface terminology conflicts and contradictions with code. This validates ubiquitous language and aligns architectural decisions with the codebase.

How do I update CONTEXT.md and ADRs inline during feature planning?▼

You update CONTEXT.md and ADRs inline by cooking a domain stress-test plan against your feature. This surfaces contradictions and updates documentation automatically as decisions crystallize during refactoring or boundary changes.

When do I need to validate domain invariants and ubiquitous language?▼

You need to validate domain invariants and ubiquitous language when planning a feature, refactoring, or touching domain boundaries. This ensures terminology consistency and aligns decisions with the codebase during changes.

What is the best way to surface contradictions between architectural decisions and code?▼

The best way to surface contradictions between decisions and code is to stress-test the domain model across context maps. This aligns your ubiquitous language and contract surfaces by validating invariants against the codebase.

Can I use a context map to check ownership boundaries across different domains?▼

Yes, you can use a context map to check ownership boundaries by cross-checking domain invariants across contexts. This process maintains coherent contract surfaces and surfaces contradictions when domain boundaries change.

Related Skills

Explore More Software Engineering Skills→
scott-rcscott-rc

ubiquitous-language

Extract domain terminology from conversations into a structured glossary file.

Community
Intermediate
jhlee0409jhlee0409
7

afc:architect

Analyze codebase architecture and record architectural decisions.

Community
Advanced
OneWave-AIOneWave-AI
245

conversation-archaeologist

Extract writing style, goals, and preferences from past Claude conversations.

Official
Advanced
wachawowachawo

ubiquitous-language

Extract domain-specific terminology from technical conversations into a UBIQUITOUS_LANGUAGE.md glossary.

Community
Intermediate