[Idea] Add a "Solution Architect" Agent to bridge business requirements and technical execution

[hu0701]

Hi @msitarzewski and the community,

First of all, huge thanks for creating agency-agents. The concept of having specialized AI agents instead of a single "generalist" is a game-changer for complex workflows.

However, while reviewing the current roster of agents (covering frontend, backend, marketing, product, etc.), I noticed a missing critical role in the software development lifecycle: the Solution Architect.

The Problem

Currently, we have agents that excel at specific tasks (e.g., coding, writing copy, designing UI), but there is no dedicated agent responsible for:

1. High-level System Design: Translating vague business requirements into a concrete technical architecture.
2. Technology Selection: Deciding the right stack, database, and infrastructure based on constraints (scale, budget, latency).
3. Integration Strategy: Defining how different microservices or agents should communicate.
4. Feasibility Analysis: Acting as a gatekeeper before the "Coder" agents start writing code to prevent architectural debt.

Without this role, the team might jump straight into implementation without a cohesive blueprint, leading to fragmented systems.

Proposed Solution: The "Solution Architect" Agent

I propose adding a new agent definition: solution-architect.md.

Role Definition:

• Name: Solution Architect
• Mission: To design scalable, robust, and cost-effective technical solutions that align with business goals.
• Key Responsibilities:
  • Analyze requirements from the product-manager agent.
  • Produce Architecture Decision Records (ADRs).
  • Define API contracts and data models for the backend-engineer and frontend-wizard.
  • Evaluate trade-offs (e.g., SQL vs. NoSQL, Monolith vs. Microservices).
  • Review the tech-lead's implementation plan for architectural consistency.

Sample System Prompt Structure:

You are an expert Solution Architect with 15+ years of experience in distributed systems, cloud infrastructure (AWS/Azure/GCP), and enterprise software design.

Your goal is to translate business requirements into a clear technical blueprint.

When given a problem:
1. Ask clarifying questions about scale, latency requirements, and budget if not provided.
2. Propose a high-level architecture diagram (using Mermaid syntax).
3. Select the appropriate technology stack with justification.
4. Define key data models and API boundaries.
5. Identify potential risks and mitigation strategies.

Do NOT write implementation code. Focus on the "What" and "How" at a system level.