skills.rest
machenjie
machenjieCOMMUNITY
Explore all skills by this author →
GitHub

domain-object-identification

Identify domain objects and map persistence, permissions, events, and tests.

4|Updated May 16, 2026
Search Tags:#authorization#domain modeling#ownership#domain-driven design#invariants#lifecycle modeling#aggregate boundaries
One-click install
npx skills add https://github.com/machenjie/rd-skills --skill domain-object-identification
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: domain-object-identification
Source: https://github.com/machenjie/rd-skills/tree/main/src/foundation/capabilities/domain-object-identification
Command: npx skills add https://github.com/machenjie/rd-skills --skill domain-object-identification

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Domain-object-identification prevents domain changes from being implemented against confusing or accidental boundaries by creating an explicit inventory of entities, value objects, aggregates, resources, ownership, lifecycle, invariants, and relationships.

Core Features & Use Cases

  • Domain object inventorying: Produce a domain model inventory covering identity, equality semantics, lifecycle, invariants, relationships, and aggregate boundaries.
  • Ownership and exposure clarity: Assign domain ownership (business owner, data owner, tenant scope, mutation authority) and distinguish internal aggregates from externally exposed resources.
  • Change impact alignment: Ensure persistence, permissions, event semantics, and test ownership can be mapped to explicit domain concepts rather than storage tables or UI labels.
  • Quality gate validation: Confirm the inventory is complete only when rules, state transitions, permissions, and events can be assigned to explicit domain owners.

Quick Start

Use domain-object-identification to generate a domain object inventory for a proposed change so you can assign invariants, lifecycle transitions, permissions, event implications, and test responsibilities to named owners.

Frequently Asked Questions about domain-object-identification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clarify domain boundaries and consistency rules before designing behavior?▼

To clarify domain boundaries before designing behavior, you need to create an explicit inventory of entities, value objects, aggregates, and invariants that defines ownership and consistency rules across your product domain.

What is the best way to assign ownership and lifecycle transitions to domain objects?▼

Assigning ownership and lifecycle transitions requires mapping business owners, mutation authority, and tenant scope to a complete domain model inventory, ensuring state transitions and permissions align with explicit domain concepts.

How does domain modeling prevent changes from being implemented against accidental boundaries?▼

Domain modeling prevents accidental boundaries by distinguishing internal aggregates from externally exposed resources, ensuring persistence, permissions, and event semantics map to explicit domain owners rather than storage tables or UI labels.

When do I need to produce a domain object inventory for a product change?▼

You need a domain object inventory when domain boundaries must be clarified before designing persistence, authorization, events, or tests, ensuring rules and state transitions can be assigned to named owners as a quality gate.

Can I map authorization and event implications using domain-driven design?▼

Yes, mapping authorization and event implications involves identifying resources, ownership, and aggregate boundaries within your domain model, allowing permissions and event semantics to be assigned to explicit domain owners.

Related Skills

Explore More Product & Management Skills→
ljucaskljucask
1

pm-domain-analysis

Generate structured domain analysis and regulatory requirement documents from product research inputs.

Community
Advanced
TheSethRoseTheSethRose

security-requirement-extraction

Translates threat models and business context into concrete, testable security requirements with traceability and compliance mappings.

Community
Advanced
KotlinKotlin
14

domain-decomposition-api-design-advisor

Derive domain boundaries and API contracts for Kotlin + Spring systems.

Official
Advanced
0xharryriddle0xharryriddle
3

m09-domain

Classify domain concepts and map them to Rust ownership patterns.

Community
Advanced