aggregate-designer

Domain aggregate design derives aggregate boundaries, invariants, policies, and read paths from explicit event flows. The skill automates this by aligning event-storming outputs into a structured markdown document for consistent bounded context design.

Separating invariants and policies in DDD aggregate documentation involves defining business rules as invariants and cross-aggregate reactions as policies. The skill enforces this required structure, generating dedicated sections to keep aggregate boundaries and external dependencies clearly isolated.

Exposed queries and read models are defined by identifying read contracts and cross-checking them with screen-inventory signals. The skill enforces an Exposed Queries section to ensure read paths reflect real usage within the bounded context.

Yes, design-level aggregate documents can be generated for Core, Supporting, and Generic contexts within a bounded context. The skill targets these varied subdomains to produce standardized markdown artifacts for each specified aggregate.

No external dependencies are required to plan and publish domain aggregate designs. The skill operates independently with its internal references component to enforce the required document structure, domain events, and read models.

Generated DDD aggregate documentation should be saved to docs/shared/contexts/<bc>/<aggregate>.md. The skill produces a single markdown document at this path so stakeholders can easily reference the aggregate design.