Skills event-sourcing-architect
📦

event-sourcing-architect

Content revision r2 Safe ⚙️ External commands

Design Reliable Event-Sourced Systems

Complex domains need traceable state changes, resilient workflows, and query models built for their access patterns. This skill guides practical event sourcing and CQRS decisions.

Supports: Claude Codex Code(CC)
🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "event-sourcing-architect" from https://skillstore.io/skills/sickn33-event-sourcing-architect.md and its manifest at https://skillstore.io/api/skills/sickn33-event-sourcing-architect/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Test it

Using "event-sourcing-architect". Design an event-sourced order aggregate with cancellation support.

Expected outcome:

The Order aggregate records placement, item changes, confirmation, and cancellation as facts. Cancellation rules depend on prior events and publish projection updates.

Using "event-sourcing-architect". Plan payment and inventory coordination for checkout.

Expected outcome:

A checkout saga correlates reservations and payment authorization. It retries transient failures, times out stalled steps, and compensates completed reservations after terminal failures.

Using "event-sourcing-architect". Prepare a versioning plan for an existing customer event.

Expected outcome:

Keep committed events immutable. Introduce a new version, define deterministic upcasting, rebuild projections in staging, and compare results before production rollout.

Security Audit

Safe
v5 • 7/24/2026 Open versioned report

The only static finding is a false positive caused by Markdown backticks around related skill names. The skill contains architectural guidance and no executable commands or malicious instructions.

1
Files scanned
72
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (1)
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-event-sourcing-architect/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-event-sourcing-architect/security.svg)](https://skillstore.io/skills/sickn33-event-sourcing-architect?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-event-sourcing-architect?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-event-sourcing-architect/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-event-sourcing-architect.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). event-sourcing-architect security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-event-sourcing-architect/audits/5

BibTeX citation

@techreport{sickn33-sickn33-event-sourcing-architect-2026, author = {sickn33}, title = {event-sourcing-architect security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-event-sourcing-architect/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "event-sourcing-architect security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-24" url: "https://skillstore.io/skills/sickn33-event-sourcing-architect/audits/5" identifiers: - type: other value: "skillstore:sickn33-event-sourcing-architect:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Model an Auditable Domain

Define aggregates, commands, and events for systems that require complete state histories and temporal queries.

Build CQRS Read Models

Plan projections, replay behavior, and idempotent handlers for application-specific query needs.

Coordinate Distributed Workflows

Design sagas with durable state, retries, timeouts, and compensating actions across services.

Try These Prompts

Map an Event-Sourced Aggregate
Map an event-sourced aggregate for [domain]. Identify commands, immutable events, aggregate boundaries, and one read model. Explain each choice.
Design a CQRS Architecture
Design a CQRS architecture for [system]. Define write flows, event streams, projections, consistency expectations, idempotency controls, and failure handling.
Plan a Distributed Saga
Design a saga for [workflow] across [services]. Include steps, correlation identifiers, retries, timeouts, compensating actions, and observable failure states.
Review an Evolving Event System
Review this architecture: [details]. Propose event versioning, upcasting, snapshotting, projection rebuilds, temporal queries, disaster recovery, and a staged validation plan.

Best Practices

  • Model events as immutable business facts with stable identifiers and clear ownership.
  • Make handlers idempotent and propagate correlation identifiers through every workflow step.
  • Test projection rebuilds, schema changes, and recovery procedures before production use.

Avoid

  • Do not mutate or delete committed production events to correct business state.
  • Do not introduce event sourcing when simple transactional CRUD meets the requirements.
  • Do not let projections become authoritative write models or hide consistency expectations.

Frequently Asked Questions

When should I choose event sourcing?
Choose it when the domain needs audit history, temporal queries, complex state transitions, or durable workflow coordination.
Does this skill generate production code?
It primarily provides architecture guidance and design artifacts. Any generated implementation still requires testing, review, and adaptation to your environment.
Can it design CQRS projections?
Yes. It can map query requirements to read models, projection handlers, replay behavior, and consistency expectations.
How does it address event schema changes?
It can propose versioned events, deterministic upcasting, compatibility rules, and staged projection rebuilds.
Can it help with distributed transactions?
It can design sagas and process managers using retries, timeouts, durable state, and compensating actions.
What information should I provide?
Provide domain rules, consistency needs, query patterns, expected volume, service boundaries, failure cases, and operational constraints.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

88a8e9a07f4c54ab105c1c41b6267c287146b07b

Maintenance freshness

7/26/2026

Usage

7 downloads · 135 views

File structure

📄 SKILL.md