| name | ontology-domain-intake |
|---|---|
| description | Clarify the target domain for ontology work by defining scope, users, constraints, out-of-scope areas, and approval points before modeling starts. |
Read:
../refs/Total Guide.md../shared/references/templates.md
Use this worker skill to produce a clean scope and constraint statement.
- Begin with discovery questions if the user has not yet specified intended use, users, available data, and constraints.
- Ask the domain intake question set below before drafting scope.
- Name the domain and intended use.
- Separate in-scope from out-of-scope.
- Identify intended users, downstream systems, and data sensitivity.
- Note required standards, regulations, or internal constraints.
- Mark where human approval is required.
Ask explicitly about:
- The operational use case or service to support
- The core entities or axes that define the domain
- The data currently collected for each core entity
- The most important decisions or workflows to improve
- The boundaries of the first version
- Sensitive or regulated data elements
- Any required internal terminology or external standards
Write or refine:
../exe/<run-id>/planning/scope.md../exe/<run-id>/planning/risks.md
- do not let scope remain open-ended
- do not draft scope from the domain label alone when the intended use is still unclear
- do not hide unresolved ambiguity
- do not treat approval-sensitive constraints as optional