| name | product-content-model |
| description | Model the product concepts, objects, actions, states, and terminology users must understand, then map language consistently across the interface. |
Product Content Model
Use when this procedure is the primary professional method needed for the assignment.
Procedure
- Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
- Establish the evidence baseline using product model, research language, UI inventory, support queries, docs terminology, and localization constraints. Do not fill material gaps with assumptions when they can change the result.
- Inventory domain terms, identify user mental models, choose canonical labels, define state/action grammar, and document exceptions where precision requires them.
- Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
- Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
- Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.
Quality gate
The same concept is named consistently and distinct concepts are not collapsed into convenient but misleading labels.