Skip to content

docs: expand software architect architecture guidance#535

Open
youngledo wants to merge 1 commit into
msitarzewski:mainfrom
youngledo:docs/software-architect-ddd-architecture-patterns
Open

docs: expand software architect architecture guidance#535
youngledo wants to merge 1 commit into
msitarzewski:mainfrom
youngledo:docs/software-architect-ddd-architecture-patterns

Conversation

@youngledo
Copy link
Copy Markdown

@youngledo youngledo commented May 18, 2026

Summary

This expands the Software Architect agent guidance around domain modeling and architectural boundary decisions.

The current agent already describes itself as specializing in domain-driven design and architectural patterns, but the body mainly covers bounded contexts, modular monoliths, microservices, event-driven architecture, and CQRS. This change makes that guidance more explicit by adding:

  • domain modeling guidance for when DDD techniques are useful vs when simple CRUD/transaction scripts are enough
  • a concise responsibility map for bounded contexts, aggregates, domain events, repositories, and anti-corruption layers
  • architecture selection guidance for layered, hexagonal, and onion architecture
  • dependency and boundary rules for keeping domain policies independent from frameworks, databases, transports, and infrastructure concerns

Why

A Software Architect is responsible for shaping the boundaries that keep a system understandable as it grows: where domain models apply, how business rules are isolated from technical mechanisms, and which architectural patterns are worth their complexity.

The existing agent already mentions domain-driven design and architectural patterns in its role description. This change makes those responsibilities more actionable by clarifying when to use DDD techniques, how core domain concepts map to architectural responsibilities, and how layered, hexagonal, and onion architecture affect dependency direction.

The goal is not to promote these patterns by default. The added guidance explicitly warns against unnecessary abstraction and recommends DDD techniques only when domain complexity justifies them.

Testing

Not run; documentation-only change.

@bensl84
Copy link
Copy Markdown

bensl84 commented May 20, 2026

Closing — this is my personal fork (bensl84/agency-agents). The canonical project lives at https://github.com/msitarzewski/agency-agents — please re-open your PR there. Thanks!

@youngledo
Copy link
Copy Markdown
Author

Closing — this is my personal fork (bensl84/agency-agents). The canonical project lives at https://github.com/msitarzewski/agency-agents — please re-open your PR there. Thanks!

Did you look at the wrong project?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants