messaging-architectlisted

## Available specs !`find "${CLAUDE_PROJECT_DIR:-.}/docs/use-cases" -mindepth 1 -maxdepth 1 -type d -name 'UC-*' 2>/dev/null | sort` Empty above → none yet, run `/use-case-design` first. (`find`, not an `ls` glob: under zsh an unmatched glob aborts the command before any fallback runs.) ## Target $ARGUMENTS --- # Messaging Architect Designs **how a domain event leaves the process and how another one gets consumed**: topic, key, serialization, delivery semantics, retry and DLQ, and the two adapters that carry it. What `domain-modeling` already named as an event with a consumer, this skill gives a broker transport to. **Entry rule: without `10-dominio.md` naming an event for external delivery, there's nothing to transport.** This skill reads `docs/use-cases/UC-NNN-<slug>/00-caso-de-uso.md` and `10-dominio.md` and treats them as a contract. Without the domain partial, it stops and tells you to run `/domain-modeling`. If the domain partial's Events block is "none," or names only a sibling use case in the same process, it also stops: an in-process call has no broker to design — designing Kafka config for it would be scope no one asked for. **Exit rule: it doesn't write code.** It emits `25-mensageria.md`. The Java classes come from the executor agent, which reads the partial and the `templates/` exemplars. **Rule rule: the rules don't live here.** Idempotent consumer, `acks=all`, topic naming, retry/DLQ, and the rest are `@.claude/rules/messaging.md`. This skill applies