Build a project glossary with AI
Agree on the meanings of ambiguous project terms and record them where the team can find them. Capture the reason behind a consequential decision when it matters.
To build a project glossary with AI, bring a term that has caused a real misunderstanding. The domain-modeling skill examines the word in context, tests possible definitions against concrete cases and records the agreed meaning in the project.
In a ticketing system, a reservation and an issued ticket may look identical until a payment expires. That example gives the team something firmer to discuss than competing dictionary definitions. Separate contexts can keep their own terms, with a map showing where each glossary lives.
What it does
- Clarify an overloaded word using examples.
- Test a definition against an unusual case.
- Record a preferred project term and its alternatives.
- Place terms in the appropriate project context.
- Capture a significant trade-off in a short decision record.
Install and use
- Install the skill in a compatible agent with access to the project and permission to edit its documentation.
- Ask “We use reservation in two different ways. Test our definition against a booking that expires before payment.”
- Review the examples together, then inspect the agreed glossary entry and any decision record the trade-off warrants.
FAQ
Source
Made by Matt Pocock. Original skill: domain-modeling, published on GitHub under the MIT licence.
View on GitHub