Choose a focused design pattern
Compare domain experts, workflow automators and quality reviewers as starting points for agent design.
The domain expert
This pattern contributes deep knowledge in one area. The image uses infrastructure as an example: security requirements, configurable values, tagging and naming conventions become explicit review criteria. Expertise should be bounded by the team's real platform standards.
The workflow automator
A release-preparation agent can analyze changes, propose a version, prepare release notes and report evidence. Distinguish preparation from publication. Shipping a release or modifying production needs separate authorization, not merely a prompt that sounds confident.
The quality reviewer
The image's accessibility reviewer considers semantics, keyboard interaction, contrast, screen-reader use and focus. An agent can surface likely problems, but a review is not an enforced merge gate until repository checks or review rules require it.
Pick one pattern, define its input and output, then restrict its tools. Reuse shared instructions or skills instead of building one agent that owns every stage. Pictured model choices and tool names are examples, not current recommendations.