event-driven-design-skill

To document an event-driven architecture for Confluence, you can generate a structured Solution Intent section containing Event Taxonomy, Topic Design, and Consumer patterns formatted as ready-to-publish Markdown.

Design event taxonomy and Kafka topics using a standard-compliant, Kafka-first approach that structures domain events and topic configurations aligned with enterprise defaults and CloudEvents 1.0.

Yes, the event-driven design approach works with CloudEvents 1.0 by generating an Event Taxonomy and Topic Design that aligns event metadata and messaging structures directly with the CloudEvents specification.

Yes, you can use this for standalone event design analysis to assess asynchronous architectures independently, generating structured consumer patterns and open event design questions without full Solution Intent documentation.

To flag standard deviations in event-driven architecture design, load enterprise standard reference files during generation, and the output will explicitly cite the specific file and section where any deviation occurs.

You should not use an event-driven architecture if your system does not rely on asynchronous communication patterns like pub/sub, event streaming, or domain events, as the generated design focuses on Kafka-style topic and consumer structures.