--- title: "ontology-forge" description: "Design and extend a Palantir Foundry ontology the domain-driven way: interview the domain, shape object types, links, interfaces and actions, then map source data and logic onto them." canonical: https://agentpluginsdirectory.com/plugins/ontology-forge last-updated: 2026-10-07 --- # ontology-forge Design and extend a Palantir Foundry ontology the domain-driven way: interview the domain, shape object types, links, interfaces and actions, then map source data and logic onto them. - Slug: ontology-forge - Publisher: pproenca - Repository: https://github.com/pproenca/dot-plugins - Manifest: plugins/ontology-forge/plugin.json - Version: 0.16.9 - License: MIT - Category (editorial): databases - Skills: 8 (audit-ontology, design-ontology, extend-ontology, forge, map-sources, ontology-forge, understand-domain, write-contracts) - MCP servers: 0 - Stars: 0 - Repository created: 2026-08-23 - Repository last pushed: 2026-09-06 - Publisher type: User - Listing: https://agentpluginsdirectory.com/plugins/ontology-forge - Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json ## What ontology-forge does, in the publisher's words Design and extend a Palantir Foundry ontology the domain-driven way. Ontology design runs in four stages, and the order is the whole point: 01 Understand the domain → 02 Design the ontology → 03 Map source data and logic → 04 Write the data contracts - Domain-driven design. Model the real world, not the source data. - Do not repeat yourself. Built it three times? Refactor. - Open for extension, closed for modification. Protect core types; extend around them. - Composition over deep hierarchies. Focused interfaces, implemented several at a time. From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/pproenca/dot-plugins/HEAD/plugins/ontology-forge/README.md ## Skills - audit-ontology: Use when /audit-ontology, 'audit the ontology', 'review this object model', 'check for anti-patterns', or before promoting a model to production. Fans out parallel reviewers across the anti-pattern catalog and structural guidance, verifies each finding against the actual files, and reports ranked v… - design-ontology: Stage 02 of ontology design. Use when /design-ontology, 'design the ontology', 'model this domain', or turning a domain understanding into object types, properties, link types, interfaces and action types. Produces the ontology YAML specification with every element named in business language, check… - extend-ontology: Use when /extend-ontology, 'extend the ontology', 'add X to the model', or fitting a new requirement into an ontology that already exists. Finds where the requirement belongs, and prefers extending through new linked types and interfaces over modifying established core types, so applications built… - forge: The entry point for ontology work. Use when /forge, 'start an ontology', 'continue the ontology', 'resume the model', 'where were we', 'what is the next step', or whenever the user wants the ontology workflow driven for them rather than having to name a stage themselves. Reads ontology/STATUS.md, r… - map-sources: Stage 03 of ontology design. Use when /map-sources, 'map source data', 'back these object types with datasets', or deciding whether logic belongs in an action, a pipeline, a function, or a derived property. Maps real datasets and columns onto an existing object model, records what was deliberately… - ontology-forge: Use whenever work touches an ontology, object model, or domain model, designing object types, properties, links, interfaces or action types; naming entities; deciding what becomes an object versus a property versus a link; or mapping source datasets onto a model. Also use for Palantir Foundry onto… - understand-domain: Stage 01 of ontology design. Use when /understand-domain, 'understand the domain', starting an ontology from scratch, or when a model is being proposed before anyone has established what the domain actually contains. Interviews the user as a domain expert, separates entities from events from decisi… - write-contracts: Stage 04 of ontology design. Use when /write-contracts, 'write the data contracts', 'ODCS contract', 'Open Data Contract Standard', 'contract for this dataset', or pinning down what an upstream source guarantees and what the ontology guarantees its consumers. Writes contracts strictly conforming to… Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.