---

name: architect description: Create comprehensive technical design documents in Chinese for software projects. Use when the user requests technical architecture design, system planning, or needs a detailed technical specification document (技术方案设计.md). Focus on gathering requirements, analyzing context, and producing structured design documents with architecture diagrams, component specifications, and implementation plans. license: Proprietary

Technical Design Architect

Create detailed technical design documents (技术方案设计.md) for software projects by gathering requirements, analyzing context, and producing comprehensive specifications.

When to Use This Skill

Use this skill when the user:

• Requests technical architecture design or system planning
• Needs a detailed technical specification document
• Wants to break down complex requirements into actionable steps
• Asks for system design or technical solution planning

Workflow

1. Information Gathering

Gather context about the project and requirements:

• Read existing project files to understand current state:

  • package.json, Cargo.toml, requirements.txt - identify tech stack
  • Existing source code - understand current architecture and patterns
  • Documentation files - capture existing requirements and constraints

• Ask clarifying questions to understand:

  • Project goals and objectives
  • Business requirements and constraints
  • Technical constraints (performance, scalability, security)
  • Non-functional requirements (availability, maintainability)
  • Integration points with existing systems
  • Timeline considerations

2. Analysis

Analyze the gathered information:

• Identify core components and their relationships
• Determine appropriate architecture patterns
• Identify potential risks and technical challenges
• Consider trade-offs for different approaches

3. Document Creation

Create a concise technical design document using the template:

Copyassets/技术方案设计.md

The document should follow this simplified structure:

• 术语表 - 技术术语解释（放在文档顶部）
• 一、背景 - 介绍问题、使用场景
• 二、目标 - 设计目的和达成效果（可衡量）
• 三、方案 - 技术方案详情
  • 方案描述
  • 整体架构（带 Mermaid 架构图）
  • 业务流程（带 Mermaid 流程图）
• 四、核心模块/核心业务流程 - 核心模块或业务流程的职责和依赖关系
• 五、附录 - 参考资料

4. Visual Documentation

Include Mermaid diagrams to visualize important aspects:

• System Architecture: Use block diagram to show high-level architecture and module relationships
• Sequence Diagram: Illustrate key workflows and business processes

Important: Avoid using double quotes ("") and parentheses () inside square brackets ([]) in Mermaid diagrams to prevent parsing errors.

5. Review and Refine

After creating the initial document:

• Verify all requirements are addressed
• Ensure architectural decisions are justified
• Check that diagrams are clear and accurate
• Confirm the implementation plan is actionable
• Ask the user for feedback and iterate

Tool Adaptation Notes

• Use read, glob, grep tools for information gathering
• Use memory tools to track project context and decisions
• Use write and edit tools to create and refine documents
• Use question tool for clarifying requirements
• Use todowrite to create tasks for implementation planning

Best Practices

• Be Thorough: Don't skip requirements gathering - insufficient context leads to poor designs
• Be Clear: Use precise language and avoid ambiguity
• Be Practical: Design should be implementable, not over-engineered
• Be Adaptive: Adjust the document structure based on project complexity
• Be Visual: Use diagrams to communicate complex ideas effectively
• Use Chinese: Write the technical design document in Chinese as requested
• Code in English: Keep code examples and technical terms in English for consistency

Output Location

Save the technical design document as:

Copy技术方案设计.md

Place it in the project root or a /plans directory if it exists.