Build and maintain project domain glossaries and architecture decision records.
npx skills add https://github.com/MSC72m/DevForge --skill domain-modeling-msc72m
Please help me install this Agent Skill. Skill: domain-modeling Source: https://github.com/MSC72m/DevForge/tree/main/skills/domain-modeling Command: npx skills add https://github.com/MSC72m/DevForge --skill domain-modeling-msc72m
High-intent search queries and answers about installing and using this skill.
Create a CONTEXT.md file at the repo root listing canonical terms with one or two sentence definitions and an _Avoid_ list of rejected synonyms. Add terms lazily as they are resolved during design discussions, keeping the file free of implementation details.
Write an ADR only when a decision is hard to reverse, surprising without context, and the result of a genuine trade-off between alternatives. Store ADRs in docs/adr/ with sequential numbering like 0001-slug.md, and keep them as short as a single paragraph.
Create a CONTEXT-MAP.md at the repo root listing each context, where its CONTEXT.md lives, and how contexts relate to each other. Each context keeps its own glossary and can maintain context-specific ADRs in its own docs/adr/ directory.
Only terms specific to the project's domain belong in CONTEXT.md, defined in one or two sentences describing what the term is. General programming concepts like timeouts or error types should be excluded even if the project uses them extensively.
Skip an ADR when a decision is easy to reverse, unsurprising to a future reader, or had no real alternative. Recording obvious or reversible choices adds noise without preserving useful reasoning.
ishandutta2007Stress-test plans against CONTEXT.md terminology and ADR decisions.
nperepichkaBuild and refine project domain models through CONTEXT.md glossaries and ADRs.
j5ik2oDetects unregistered domain terms and ADR candidates in Kiro specs and syncs them to CONTEXT.md.
taiyousan15Guide Event Storming workshops and generate Markdown domain reports.
