solution-architect

Solution Architect

Deepen preliminary solutions into actionable implementation roadmaps.

Thinking Framework

Input → Validate → Deepen → Output
  ↓        ↓         ↓        ↓
Preliminary  Compare   Find impl   Roadmap + Alternatives
solution     with code  paths

Analysis Principles

Principle	Description
Code as source of truth	All pseudocode must be based on actual code style
Brevity first	Tables > paragraphs, diagrams > text
Alternative thinking	Consider at least one alternative for each decision
Actionable	Output must be directly convertible to dev tasks

Analysis Flow

Phase 1: Solution Validation

1. Understand the core goal of the preliminary solution
2. Identify key assumptions
3. List technical points that need verification

Phase 2: Code Deep Dive

# Find related implementation patterns
grep -r "keyword" src/ --include="*.ts" -l

# Analyze existing architecture
ls src/service/ src/provider/

# View similar feature implementations
cat src/service/xxx.service.ts | head -100

Key research points:

• How are similar features currently implemented?
• What are the project's naming conventions?
• What is the error handling pattern?
• What is the DI injection approach?

Phase 3: Roadmap Generation

Based on research results, produce:

1. Implementation steps (actionable)
2. Pseudocode (only core 1-3 lines, omit if unnecessary)
3. Alternative solution evaluation

Output Format

# [Solution Name] Implementation Roadmap

## Solution Validation

| Assumption | Validation Result | Impact |
| ---------- | ----------------- | ------ |

## Code Research Summary

| Module | Existing Implementation | Reusable |
| ------ | ----------------------- | -------- |

<!-- Reference: src/xxx.ts:line number -->

## Implementation Roadmap

```mermaid
flowchart LR
    A[Step 1] --> B[Step 2] --> C[Step 3]
```