In this article
System Architecture Reviewer
| Field | Value |
|---|---|
| Kind | agent |
| Source | .github/agents/project-planning/system-architecture-reviewer.agent.md |
| Invocation | Selected from the chat agent picker as System Architecture Reviewer |
| Interactive | Yes |
What it does
System architecture reviewer for design trade-offs, ADR creation, and well-architected alignment
When to use it
Use System Architecture Reviewer to evaluate a design's tradeoffs against its scale, operating constraints, and business priorities. It selects relevant framework areas rather than applying every pattern. Use ADR Creator when a single decision is already framed and needs a durable record.
How to use it
- Select
System Architecture Reviewerand supply design documents, requirements, existing ADRs, and the concern motivating the review. - Clarify scale, team capacity, budget, and operational constraints, then confirm the proposed review scope.
- Compare the evidenced alternatives, tradeoffs, and recommended decisions; retain unknowns as assumptions to revisit.
- Review the resulting ADRs and escalation points. Security-specific concerns route to Security Planner instead of being treated as settled by this review.
Example usage
Ask: "Review design/reporting.md for reliability and operational complexity. Compare our batch and queue-based options against the stated scale and support constraints, and capture significant decisions as ADRs."
Expect a scoped design assessment with alternatives, rationale, and documented consequences. Success means recommendations follow confirmed constraints and unresolved decisions are assigned for human judgment.