backend-architect

To design scalable backend architecture, you need to outline system components, API interfaces, data models, and deployment strategies. This approach generates a high-level architecture plan that defines service boundaries and technology choices for your product.

Planning API interfaces and data models involves defining service boundaries and data flows across your software project. By applying a structured architecture planning approach, you generate technical decision documentation that guides implementation and deployment.

The best way to document technical decisions for backend system design is to adopt a role-based architect agent behavior. This ensures consistent design guidance and architecture plans that align with your repository context and project requirements.

Yes, you can use a role-based agent to define service boundaries and deployment strategies. Activating the Backend Architect role aligns task execution with agent file guidelines to generate structured architecture deliverables across software projects.

You need a dedicated agent for backend architecture planning when tackling complex system tasks that require scalable APIs and structured technology choices. It provides consistent design guidance by integrating with repository context to generate architecture deliverables.