ubiquitous-language

Drive a focused interview with the user about the domain vocabulary they use, then write the result into the bounded-context CONTEXT.md that setup-agentic-repository scaffolded for that subdomain. The output is not a standalone UBIQUITOUS_LANGUAGE.md — it is appended into the right CONTEXT.md so other agent sessions automatically pick it up via the contract in <docs-dir>/AGENTS_CONTEXT.md (the docs dir is discovered in Phase 1; typically agents-docs/ but --docs-dir may have put it elsewhere).

The previous version of this skill wrote a sidecar file. That file is invisible to the Mimas instruction tree, so terms captured there never reach the agents reading CONTEXT.md at session start. This rewrite fixes that: the glossary lives where the contract says glossaries live.

Phase 1 — Verify prerequisites and locate the docs directory

Confirm the repo has been initialized with the Mimas template, and discover where its agent docs actually live. setup-agentic-repository writes the agent doc tree to agents-docs/ by default — kept as a sibling of any human-maintained docs/ so the two don't collide — but the user can pass --docs-dir <dir> (e.g. docs/agents) to put it somewhere else. Don't assume the path; discover it.

1. Read AGENTS.md at the repo root. Every Mimas-generated AGENTS.md lists its docs paths in the very first block (<docs-dir>/AGENT_WORKFLOW.md, <docs-dir>/AGENTS_CONTEXT.md, etc.). The directory in those paths is the docs dir for this repo.
2. If AGENTS.md doesn't exist or doesn't reference the contract files, fall back to searching for AGENTS_CONTEXT.md directly (find . -maxdepth 3 -name AGENTS_CONTEXT.md). The directory containing it is the docs dir.
3. Confirm the file you actually need is there: <docs-dir>/AGENTS_CONTEXT.md — the CONTEXT.md / CONTEXT-MAP.md contract.
4. Confirm at least one CONTEXT.md exists somewhere in the tree (root, a subdomain, or both). The CONTEXT.md files live with the code they describe, not under the docs dir.

If AGENTS_CONTEXT.md cannot be found at all, tell the user this skill is designed to run after setup-agentic-repository (which scaffolds both the contract and the CONTEXT.md skeletons) and stop. Don't try to create them yourself — that is the other skill's job.