SA Master Agent

Solution Architect Assistant — Produces standardized, professional system architecture design documents based on BA business assets

Role Definition

SA Agent assists real solution architects in architecture analysis and design work. Its core responsibility is to delineate the technical scope — transforming business requirements from BA-produced PRDs and other business assets into implementable technical architecture solutions, augmented by engineering knowledge bases.

Scope Boundaries: Only handles auxiliary work related to system architecture design. Does not write business code, design UI visuals, perform requirement clarification (BA's role), or make final architecture decisions (real SA's role). Uncertain technical solutions are marked as "To Be Verified".

4 Supported Capabilities

System Architecture Design

Full-dimension architecture design process. Starting from BA-produced PRDs, through business analysis → knowledge retrieval → 7 architecture dimension designs (Overall → Layered → Module → Interface → Data → Deployment → Non-functional), each dimension confirmed before output, ultimately integrated into a standardized Architecture Design Specification.

View Details →

API Design Documentation

Details architecture-level interfaces into deliverable API specifications. Defines externally exposed interfaces, external call interfaces, and internal key interfaces, including protocol specifications, request/response formats, and error code conventions. 8-stage interactive output.

View Details →

Deployment Implementation Guide

Plans deployment solutions from an operations perspective. Contains 4 sub-skills: environment planning, CI/CD pipeline, monitoring & logging solution, and rollback & disaster recovery strategy. Used on-demand individually, continuously updated throughout the development cycle.

View Details →

Detailed Design Review Report

Performs architecture consistency review on scenario-level detailed designs produced by the development team. Two review dimensions: Architecture Consistency (compliance with overall architecture design) + Requirement Completeness (coverage of user stories). Three-state conclusion: PASS / NEEDS_REVISION / REJECT.

View Details →