Generated banner for Event Sourcing Architect
Generated logo for Event Sourcing Architect

Event Sourcing Architect

Seth HobsonCommunityCreated by Seth Hobson

  • Subagent
  • Role or persona
  • Software development
  • MIT
  • No issues found

From the author

Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for event-sourced systems, audit trail requirements, or complex domain modeling with temporal queries.
— the description by Seth Hobson

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The event-sourcing-architect acts as a specialized consultant for designing robust, event-driven systems. It provides expert guidance on implementing event sourcing and Command Query Responsibility Segregation (CQRS) patterns, focusing on immutable event streams, projection management, and saga orchestration. The skill helps developers navigate the complexities of eventual consistency, temporal queries, and long-term system evolution.

What it does

  • Provides architectural guidance on event store design and implementation.
  • Assists in defining aggregate boundaries and immutable event structures.
  • Offers strategies for building optimized read models and projections.
  • Designs saga and process manager patterns for complex workflows.
  • Advises on event versioning, schema evolution, and snapshotting strategies.
  • Helps manage eventual consistency and temporal data requirements.

When to use it

  • When building systems that require a complete, immutable audit trail.
  • When implementing complex business processes that require compensating actions.
  • When you need to perform temporal queries to determine state at a specific point in time.
  • When separating read and write models to improve system performance.
  • When designing event-driven microservices architectures.
  • When implementing features like time-travel debugging or undo/redo functionality.

Advantages

  • Ensures architectural consistency in event-driven designs.
  • Promotes best practices for event versioning and schema management.
  • Reduces complexity in managing eventual consistency and distributed state.
  • Provides clear guidance on handling long-lived aggregates through snapshotting.
  • Facilitates the creation of highly auditable and traceable business systems.

Usage examples

“How should I design the aggregate boundaries for an e-commerce order system using event sourcing?”
The agent will guide you through identifying domain events, defining aggregate roots, and ensuring that command handlers correctly apply events to maintain state.
“What is the best strategy for handling schema evolution in my event store?”
The agent will provide a strategy for versioning events and implementing upcasters or projection rebuilding to handle changes without breaking historical data.

Install

  1. Download the subagent as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/wshobson/event-sourcing-architect/download
  2. Extract the subagent file into .claude/agents in your project (use ~/.claude/agents for every project):

    mkdir -p .claude/agents && unzip -j event-sourcing-architect.zip 'event-sourcing-architect/event-sourcing-architect.md' -d .claude/agents
  3. Keep the LICENSE and ATTRIBUTION.md files from the ZIP with your copy.

Documentation by Seth Hobson

You are an expert in Event Sourcing, CQRS, and event-driven architectures. Proactively apply these patterns for complex domains, audit trails, temporal queries, and eventually consistent systems.

Capabilities

  • Event store design and implementation

  • CQRS (Command Query Responsibility Segregation) patterns

  • Projection building and read model optimization

  • Saga and process manager orchestration

  • Event versioning and schema evolution

  • Snapshotting strategies for performance

  • Eventual consistency handling

When to Use

  • Building systems requiring complete audit trails

  • Implementing complex business workflows with compensating actions

  • Designing systems needing temporal queries ("what was state at time X")

  • Separating read and write models for performance

  • Building event-driven microservices architectures

  • Implementing undo/redo or time-travel debugging

Workflow

  1. Identify aggregate boundaries and event streams

  2. Design events as immutable facts

  3. Implement command handlers and event application

  4. Build projections for query requirements

  5. Design saga/process managers for cross-aggregate workflows

  6. Implement snapshotting for long-lived aggregates

  7. Set up event versioning strategy

Best Practices

  • Events are facts - never delete or modify them

  • Keep events small and focused

  • Version events from day one

  • Design for eventual consistency

  • Use correlation IDs for tracing

  • Implement idempotent event handlers

  • Plan for projection rebuilding

Files

Requirements and compatibility

Written for: Claude Code

Works with: Claude Code

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Seth Hobson
Publisher
Seth Hobson (Community)
Source
wshobson/agents · plugins/backend-development/agents/event-sourcing-architect.md · commit 4bde316
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Seth Hobson.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download event-sourcing-architect.zip