reactor-sub-agent

Event handlers with idempotency use unique keys to prevent duplicate processing when messages are retried. This Skill automates handler design by reading your specification files and generating skeletons that enforce idempotency keys, exponential backoff retry strategies, and transactional boundaries for both durable and ephemeral subscriptions.

Dead-letter queues (DLQ) capture events that fail after retries, preventing message loss. This Skill designs handlers that route failed events to DLQs with configurable timeouts and circuit breakers, ensuring failed events are isolated and can be analyzed without blocking the primary event stream.

Yes. This Skill reads docs/specs/, frame.yaml, and requirements/ directories to automatically generate event handler skeletons with idempotency controls, retry policies, and DLQ routing pre-configured. You provide the specification; the Skill produces validated code matching your event integration patterns.

Transactional boundaries prevent partial state changes when events are retried. This Skill validates handler implementations against your machine/reactor.yaml configuration to enforce transactional settings, ensuring idempotency keys and retry logic work within atomic transaction scopes.

After exponential backoff retries are exhausted, events move to the dead-letter queue for manual inspection. This Skill designs handlers that implement this fallback automatically, with configurable retry attempts and DLQ forwarding rules defined in your specification.