architecture-event-driven
Architecture Event Driven
Overview
Use this skill to design event-driven systems that remain correct under retries, delays, and partial failures.
Scope Boundaries
- Workflows span multiple bounded contexts or services asynchronously.
- Temporal decoupling is needed to improve autonomy or resilience.
- Integration churn is high and direct RPC coupling causes fragility.
Core Judgments
- Event semantics: fact versus command and ownership of meaning.
- Delivery guarantees: at-most-once, at-least-once, effectively-once patterns.
- Ordering strategy: global ordering, per-key ordering, or order independence.
- Recovery model: replay, dead-letter, compensating actions, and backfill.
Practitioner Heuristics
- Publish events as immutable domain facts from the source of truth.
- Never rely on "exactly-once" assumptions; design idempotent consumers.
- Partition keys must align with business consistency boundaries.
- Version event contracts with additive evolution first; reserve breaking changes for controlled migrations.
Workflow
- Define domain events and ownership boundaries.
- Specify producer guarantees and consumer idempotency requirements.
- Choose ordering and partitioning strategies by business invariant.
- Design failure-handling paths for retry storms, poison messages, and replay.
- Align observability with event lifecycle (published, consumed, failed, compensated).
- Document contract evolution and deprecation strategy.
Common Failure Modes
- Events used as remote procedure calls in disguise.
- Shared event schema controlled by consumers instead of producers.
- Unbounded retry loops causing downstream saturation.
Failure Conditions
- Stop when event ownership or semantics are ambiguous.
- Stop when consumer correctness depends on fragile global ordering.
- Escalate when replay/compensation behavior is undefined for critical flows.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9