Agent skill

Model Domain

by danielvm-git in danielvm-git/bigpowers

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates specs/tech-architecture/tech-stack.md and specs/adr/ inline as decisions crystallise.

MITAuto-check passedDevelopment

Install Model Domain

skills CLI

$ npx skills add danielvm-git/bigpowers --skill model-domain -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install danielvm-git/bigpowers model-domain --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/model-domain .claude/skills/model-domain && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "model-domain" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/model-domain into .claude/skills/model-domain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "model-domain", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/danielvm-git/bigpowers/tree/main/skills/model-domain

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add danielvm-git/bigpowers --skill model-domain -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install danielvm-git/bigpowers model-domain --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/model-domain .agents/skills/model-domain && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "model-domain" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/model-domain into .agents/skills/model-domain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "model-domain", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add danielvm-git/bigpowers --skill model-domain -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install danielvm-git/bigpowers model-domain --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/model-domain .cursor/skills/model-domain && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "model-domain" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/model-domain into .cursor/skills/model-domain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "model-domain", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/danielvm-git/bigpowers.git --path skills/model-domain

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add danielvm-git/bigpowers --skill model-domain -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install danielvm-git/bigpowers model-domain --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/model-domain .gemini/skills/model-domain && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "model-domain" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/model-domain into .gemini/skills/model-domain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "model-domain", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install danielvm-git/bigpowers model-domain

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add danielvm-git/bigpowers --skill model-domain -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/model-domain .github/skills/model-domain && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "model-domain" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/model-domain into .github/skills/model-domain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "model-domain", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add danielvm-git/bigpowers --skill model-domain -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install danielvm-git/bigpowers model-domain --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/model-domain .opencode/skills/model-domain && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "model-domain" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/model-domain into .opencode/skills/model-domain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "model-domain", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: model-domain
GitHub stars: 256
Token cost: ~1.2k tokens
SKILL.md length: 515 words
Files: 3
Skills in repo: 39
Repo updated: Sep 21, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates specs/tech-architecture/tech-stack.md and specs/adr/ inline as decisions crystallise.

Works in 3 steps: Hard to reverse — the cost of changing… → Surprising without context — a future… → The result of a real trade-off — there…
User wants to stress-test a plan against their projects domain language and documented decisions
SKILL.md covers Domain awareness, During the session and Concurrency safety audit
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Model Domain is an agent skill from danielvm-git/bigpowers. Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates specs/tech-architecture/tech-stack.md and specs/adr/ inline as decisions crystallise. Use when user wants to stress-test a plan against their project's domain language and documented decisions.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `ADR-FORMAT.md` and `CONTEXT-FORMAT.md`).

It sits in Development, covering Architecture decision records, Requirements gathering and Load testing. The repository describes itself as: Agent skills synthesizing years of software engineering discipline into a prescriptive methodology for solo developers. The licence is MIT.

When your agent uses it

User wants to stress-test a plan against their projects domain language and documented decisions
Tasks that involve Architecture decision records
Tasks that involve Requirements gathering

Example prompts

“/model-domain”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

Hard to reverse — the cost of changing your mind later is meaningful
Surprising without context — a future reader will wonder "why did they do it this way?"
The result of a real trade-off — there were genuine alternatives and you picked one for specific reasons

What it can do on your machine

Read from SKILL.md and the folder at commit 812d57a. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Model Domain loads about 1.2k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 515 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~80
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from danielvm-git/bigpowers at commit 812d57a, republished under its MIT licence (© danielvm-git). 515 words, ~1,160 tokens.

Download SKILL.mdSave it as .claude/skills/model-domain/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.

name: model-domain
description: Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates specs/tech-architecture/tech-stack.md and specs/adr/ inline as decisions crystallise. Use when user wants to stress-test a plan against their project's domain language and documented decisions.
model: sonnet
effort: standard

Model Domain

Distinct from define-language and deepen-architecture: Use this skill to stress-test a plan through a grilling interview that resolves domain model decisions and captures invariants. Use define-language to produce a canonical glossary of terms. Use deepen-architecture to find module-level refactoring opportunities in code.

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.

HARD GATE — Capture invariants (what MUST always be true) and state machines (what transitions are legal) for core entities. If these are fuzzy, design will fail.

Ask the questions one at a time, waiting for feedback on each question before continuing.

If a question can be answered by exploring the codebase, explore the codebase instead.

Domain awareness

During codebase exploration, also look for existing documentation:

File structure

Most repos have a single context:

/
├── specs/
│   ├── CONTEXT.md
│   └── adr/
│       ├── 0001-event-sourced-orders.md
│       └── 0002-postgres-for-write-model.md
└── src/

If a specs/tech-architecture/tech-stack.md exists, the repo has multiple contexts. The map points to where each one lives:

/
├── specs/
│   ├── CONTEXT-MAP.md
│   └── adr/                          ← system-wide decisions
└── src/
    ├── ordering/
    │   └── specs/
    │       ├── CONTEXT.md
    │       └── adr/                  ← context-specific decisions
    └── billing/
        └── specs/
            ├── CONTEXT.md
            └── adr/

Create files lazily — only when you have something to write. If no specs/tech-architecture/tech-stack.md exists, create it when the first term is resolved. If no specs/adr/ exists, create it when the first ADR is needed.

During the session

Challenge against the glossary

When the user uses a term that conflicts with the existing language in specs/tech-architecture/tech-stack.md, call it out immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y — which is it?"

Sharpen fuzzy language

When the user uses vague or overloaded terms, propose a precise canonical term. "You're saying 'account' — do you mean the Customer or the User? Those are different things."

Discuss concrete scenarios

When domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts.

Show full SKILL.md (211 more words)Show less

Cross-reference with code

When the user states how something works, check whether the code agrees. If you find a contradiction, surface it: "Your code cancels entire Orders, but you just said partial cancellation is possible — which is right?"

Update specs/tech-architecture/tech-stack.md inline

When a term is resolved, update specs/tech-architecture/tech-stack.md right there. Don't batch these up — capture them as they happen. Use the format in CONTEXT-FORMAT.md.

Don't couple specs/tech-architecture/tech-stack.md to implementation details. Only include terms that are meaningful to domain experts.

Offer ADRs sparingly

Only offer to create an ADR when all three are true:

Hard to reverse — the cost of changing your mind later is meaningful
Surprising without context — a future reader will wonder "why did they do it this way?"
The result of a real trade-off — there were genuine alternatives and you picked one for specific reasons

If any of the three is missing, skip the ADR. Use the format in ADR-FORMAT.md.

Concurrency safety audit

When the plan touches shared state, async, or multi-threaded code:

List every shared mutable location (globals, singletons, module-level caches).
For each: who reads, who writes, synchronization mechanism (lock, actor, immutable copy).
Flag race risks (check-then-act, non-atomic read-modify-write) with severity.
Record findings in specs/tech-architecture/tech-stack.md under ## Concurrency or in an ADR if architectural.

<!-- story: e07s03 -->

Files

SKILL.md and 2 other files in skills/model-domain of danielvm-git/bigpowers.

SKILL.md
ADR-FORMAT.md
CONTEXT-FORMAT.md

Open the folder on GitHubat commit 812d57a

Compare with similar skills

Model Domain next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Model Domain compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Model Domain this skilldanielvm-git/bigpowers	256	—	~1.2k	Automated safety check: Pass	MIT	16 days ago
Grill With Docsmeain/dotfiles	285	21 repos	~875	Automated safety check: Pass	MIT	1 mo ago
Grill With Docsayoubben18/ab-method	192	—	~2.1k	Automated safety check: Pass	MIT	6 days ago
Grill With Docsalirezarezvani/claude-skills	28k	—	~1.8k	Automated safety check: Pass	MIT	1 mo ago
Deep Divebyungjunjang/jangpm-meta-skills	121	—	~2.5k	Automated safety check: Pass	None	2 mo ago
Grill Menrwl/nx	29k	—	~1.2k	Automated safety check: Pass	MIT	today

Similar skills

Grill With Docs
meain/dotfiles
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.
285 GitHub starsUsed in 21 repos~875 tokens
DevelopmentAuto-check passed
Grill With Docs
ayoubben18/ab-method
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.
192 GitHub stars~2.1k tokensUpdated 6 days ago
DevelopmentAuto-check passed
Grill With Docs
alirezarezvani/claude-skills
Docs-anchored grilling session — challenges a plan against the project's existing language (CONTEXT.md) and recorded decisions (docs/adr/), and updates those files inline as terminology and…
28k GitHub stars~1.8k tokensUpdated 1 mo ago
DevelopmentAuto-check passed
Deep Dive
byungjunjang/jangpm-meta-skills
Socratic interview skill to deepen a spec or refine an existing agent blueprint.
121 GitHub stars~2.5k tokensUpdated 2 mo ago
Agent WorkflowsAuto-check passed
Grill Me
nrwl/nx
Grill the user relentlessly about a plan, design, decision, or set of review findings — working the decision tree in rounds until nothing is left silently assumed.
29k GitHub stars~1.2k tokensUpdated today
Agent WorkflowsAuto-check passed
Grill Me
macalbert/envilder
Grilling session that challenges a plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.
138 GitHub stars~1k tokensUpdated 2 days ago
Agent WorkflowsAuto-check passed

Questions about Model Domain

What does Model Domain do?

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates specs/tech-architecture/tech-stack.md and specs/adr/ inline as decisions crystallise. Model Domain is an agent skill from danielvm-git/bigpowers.md and specs/adr/ inline as decisions crystallise.

When should I use Model Domain?

Model Domain fits situations like: user wants to stress-test a plan against their projects domain language and documented decisions; tasks that involve Architecture decision records; tasks that involve Requirements gathering.

How do I install Model Domain in Claude Code?

Run `npx skills add danielvm-git/bigpowers --skill model-domain -a claude-code`. Or copy the skill folder (skills/model-domain in danielvm-git/bigpowers) into .claude/skills/model-domain in your project. Claude Code loads it when a task matches its description.

How do I install Model Domain in Codex?

Run `npx skills add danielvm-git/bigpowers --skill model-domain -a codex`. Or copy the skill folder (skills/model-domain in danielvm-git/bigpowers) into .agents/skills/model-domain in your project. Codex loads it when a task matches its description.

Can I use Model Domain in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add danielvm-git/bigpowers --skill model-domain -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/model-domain, .gemini/skills/model-domain, .github/skills/model-domain and .opencode/skills/model-domain in your project.

What does Model Domain need to run?

SKILL.md names no scripts, command-line tools or credentials: Model Domain is instructions for the agent only.

Does Model Domain access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Model Domain safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Model Domain use?

Model Domain is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Model Domain use?

About 1.2k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Model Domain?

Skills that share tags, products or a category with Model Domain: Grill With Docs (meain/dotfiles, 285 stars), Grill With Docs (ayoubben18/ab-method, 192 stars), Grill With Docs (alirezarezvani/claude-skills, 28k stars) and Deep Dive (byungjunjang/jangpm-meta-skills, 121 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Model Domain?

danielvm-git (a GitHub user) maintains it in danielvm-git/bigpowers, which has 256 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on September 21, 2026.

Source: danielvm-git/bigpowers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Model Domain

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Model Domain

Domain awareness

File structure

During the session

Challenge against the glossary

Sharpen fuzzy language

Discuss concrete scenarios

Cross-reference with code

Update specs/tech-architecture/tech-stack.md inline

Offer ADRs sparingly

Concurrency safety audit

Files

Compare with similar skills

Similar skills

More from danielvm-git/bigpowers

Related

Questions about Model Domain