← Explore all agents

ARCHITECTURE AND DECISIONS / wshobson

Event Sourcing Architect

Plans event-sourced systems through aggregate boundaries, immutable event records, projections, sagas and event-versioning decisions.

“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”

01 / THE REASONING

Why this made the selection.

  • Covers the practical linkage between command handling, read projections and cross-aggregate workflows.
  • Calls out idempotency, eventual consistency and projection rebuilding as design responsibilities.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • plugins/backend-development/agents/event-sourcing-architect.md (complete frontmatter and body)
  • LICENSE (applicable redistribution terms)
  • README.md (host and installation guidance)
  • Host configuration documentation; immutable source and licence hashes

Our findings

  • The workflow moves from aggregate/event boundaries to handlers, projections, sagas, snapshots and versioning.
  • Correlation identifiers, idempotent consumers and rebuilding projections are explicit concerns.
  • No tool restriction is defined, and the model is inherited from the host.

Not established by this review

  • The agent has not been executed or benchmarked.
  • Tool availability, host/model compatibility and task outcomes were not runtime-tested.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Use the role in your project.

Upstream setup instructions ↗
  1. Download the original event-sourcing-architect.md together with its LICENSE and attribution; inspect its instructions, model choice and tools.
  2. For project use, place the definition in .claude/agents/event-sourcing-architect.md; the documented personal scope is ~/.claude/agents/.
  3. Ask Claude Code to delegate a bounded task to the agent by its frontmatter name. Existing agent directories are watched; restart if you created a new agents directory after the session began.
  4. Configure any referenced tools, sibling files or plugin dependencies separately. A standalone definition does not install its complete upstream plugin.

Before you start

  • Claude Code with domain requirements, consistency needs and storage constraints.
  • A scoped design problem and project-specific test or replay infrastructure for implementation validation.

THE COMPLETE REVIEWED DEFINITION

Read it before you reuse it.

Original source bytes, with attribution.
Review the host-specific setup notes above.

---
name: event-sourcing-architect
description: 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.
model: inherit
---

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

The download contains event-sourcing-architect.md. Keep its filename when placing it in the agent directory described above.

By wshobson. Exact upstream source ↗ · Licence · Attribution

SHA-256 907c1f38973cf90e8492b767f6b05d797f55229c1539798fee2b552e3c6fdc5b

Read the applicable licence
MIT License

Copyright (c) 2024 Seth Hobson

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE. 

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/wshobson/agents/blob/4236bb91f8395b0435f1d8b8baf9e8e4c69a8620/plugins/backend-development/agents/event-sourcing-architect.md

    Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, access

  2. https://github.com/wshobson/agents/blob/4236bb91f8395b0435f1d8b8baf9e8e4c69a8620/LICENSE

    Supports: license, artifact

  3. https://github.com/wshobson/agents/blob/4236bb91f8395b0435f1d8b8baf9e8e4c69a8620/README.md

    Supports: compatibility, install

  4. https://code.claude.com/docs/en/sub-agents.md

    Supports: compatibility, install, access, review, limitations