
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures
by wshobsonFree
Description
cqrs-implementation is an agent skill from the wshobson/agents collection for implementing Command Query Responsibility Segregation, or CQRS, in a software system. CQRS splits the part of an application that changes data, the commands, from the part that reads it, the queries, so each side can have its own model, storage and scaling. The skill explains the CQRS architecture and the core concepts behind it, and it covers the situations where the split pays off: separating read and write concerns, scaling reads independently of writes, optimizing complex queries, and supporting high-performance reporting where the read model needs a different shape from the write model. It also covers event-sourced systems, where changes are recorded as events and read models are built from them, which is a common partner for CQRS. The skill helps an agent design the two sides and the way they stay in step, and it is most useful when a team has already found that one model cannot serve both writes and reads well. It is installed with the skills CLI from the wshobson/agents repository. Its skills.sh page showed about 10.8K installs and passing results from three security audits at the time of the scan.…
Highlights
- CQRS architecture guidance
- Separate read and write models
- Independent read scaling
- Query optimization for complex scenarios
- Event-sourced system support
- Installs with the skills CLI
Ratings & Reviews
No ratings yet
Be the first to rate cqrs-implementation.
People also visit

python-design-patterns
Fundamental design principles for writing maintainable, testable Python code

python-project-structure
Python project organization, module architecture, and public API design

acquire-codebase-knowledge
The user explicitly asks to map, document, or onboard into an existing codebase

architecture-blueprint-generator
Analyzes codebases to generate comprehensive architectural documentation
cqrs-implementation FAQ
What is CQRS?
Command Query Responsibility Segregation: writes and reads are handled by separate models, so each can be designed and scaled for its own job.
When should I use it?
When reads and writes need different models, when reads must scale on their own, or when reporting needs a shape the write model does not provide.
Does it cover event sourcing?
Yes. The skill covers building event-sourced systems, which often pair with CQRS.
Is it only for large systems?
The skill is aimed at scalable architectures, so it is most useful where a single model is clearly struggling with reads or writes.
How do I install it?
Run npx skills add https://github.com/wshobson/agents --skill cqrs-implementation.
What security audits does it have?
skills.sh lists three audits: Gen Agent Trust Hub Pass, Socket Pass and Snyk Pass.
What are the best cqrs-implementation alternatives?
Popular alternatives to cqrs-implementation include event-store-design, projection-patterns and python-design-patterns. See all cqrs-implementation alternatives




