Terminal
Terminal/Skill
Builds a shared project language and bounded contexts before coding, producing a CONTEXT.md glossary and decision records so your agent keeps domain names consistent.
By Rohit Ghumare
Works with
npx skills add rohitg00/pro-workflow --skill domain-modelingMost misbuilds start as a language gap: the agent is dropped into a project and left to infer the jargon, so it uses twenty words where the domain has one. A shared language closes the gap. When code, conversation, and the model all draw from the same vocabulary, names line up, navigation gets cheaper, and the model spends fewer tokens reasoning because it has a tighter language to reason in.
CONTEXT.md - the shared-language glossary. One term per line:
term - what it means in this project. Grouped by bounded context when
there is more than one. Point every future session at this file. On re-run,
add new terms and update definitions that changed; do not rewrite the file
wholesale.docs/decisions/NNNN-slug.md for the contested
modeling calls only. Read the directory first and number from the highest
existing record so two records never collide. Skip the obvious ones.Run this before plan-interrogate on a new area, or let plan-interrogate
call back here when it hits terms it cannot pin. The CONTEXT.md this produces
is the same file plan-interrogate emits - one shared-language artifact, two
ways in.