Domain modeling

Own the project's domain vocabulary and decision records, whether invoked directly or by another workflow. Keep operating context, collaboration preferences, and permissions in their existing project/workflow documents. Modeling does not authorize application changes or a broader architecture redesign.

Use normal file-reading and editing tools; no specific SDK, literal Skill tool, subagent, or model service is required. Loading this skill grants no mutation permission.

1. Establish scope and authority

Check applicable project instructions and the actual agreement once per context, reusing already-read guidance and following relevant context/authority pointers and directory/runtime restrictions. Compare decision/effect authority, safety, verification, documentation and continuation guidance with this work. Equivalent existing layouts need no Setup provenance or template. Identify specific absent, conflicting or unverifiable guidance and recommend explicit setup/reconciliation without invoking it or rewriting policy. Missing common guidance blocks dependent project modeling; missing optional tracker/model detail blocks only that capability. Do not create empty domain records to satisfy prerequisites.

For a caller handoff, read the handoff contract before proceeding. For direct use, establish the same inputs from the request and project instructions: target, affected subject, evidence, document homes, decision authority, exclusions, and plan-only or approved mode. Confirmed glossary/context-map maintenance can use the current task and project agreement's existing authorization; do not demand repeated approval of that unchanged delta. ADR creation or change requires explicit user agreement and permission, including proposed drafts. If mutation authority is unclear, use plan-only and ask only for the missing authorization.

Read applicable instructions, the project's documentation ownership policy, existing glossary/context map, relevant ADRs and specs, and code using the affected concepts. Inspect current work and symlinks before choosing edit targets. Reuse valid document homes and confirmed decisions; a caller's mapping takes precedence over default paths unless it conflicts with existing authority, in which case return the conflict.

Done: the bounded subject, authoritative sources, current state, mode, and allowed writes are known; missing evidence or authority is explicit.

2. Resolve the model

When terms, relationships, or context boundaries need work, read vocabulary and context maps. When an architectural choice needs recording or reconsideration, read decision records. Apply only the relevant branch; neither a glossary nor an ADR is mandatory output.