SKILL.md
Domain Context and Decision Handoff
Govern “what these business terms mean” separately from “why this option was chosen.” Do not create an empty shell when no stable content exists.
Domain Context Artifact: Domain Language Only
When terms require repeated explanation, one term has multiple meanings, or unclear language causes module-boundary errors, first reuse the repository's existing glossary/domain-model document or the context role in .governance/docs-map.json. Only when no equivalent exists should you lazily create the default CONTEXT.md from templates/context.example.md.
Record only:
- domain terms and precise definitions;
- relationships among core concepts;
- confirmed ambiguities and the chosen interpretation;
- ambiguities still awaiting confirmation from a domain owner.
Do not include implementation details, current state, task schedules, full requirements, decision rationale, or history. Keep those in code/MAP, STATUS/Issue Tracker, Spec, ADR, and LOG respectively. Terms must be traceable to code, contracts, or business evidence. Mark unconfirmed items as needs confirmation; do not guess.