docs: expand software architect architecture guidance#535
Open
youngledo wants to merge 1 commit into
Open
Conversation
|
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! |
Author
Did you look at the wrong project? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
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.