client-arch-explain

tikazyq's avatarfrom tikazyq

生成客户友好的架构说明(通俗语言解释架构层次、数据流、技术选型),适合演示和评审会议。当准备客户演示或用户验收前使用。

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 3, 2026

When & Why to Use This Skill

The client-arch-explain skill bridges the gap between complex technical engineering and business communication. It automatically transforms intricate system architectures, data flows, and technology stacks into layman-friendly explanations using analogies and business-value-driven language, making it an essential tool for architects and PMs to align with non-technical stakeholders.

Use Cases

  • Client Demos & Presentations: Convert high-level technical diagrams into relatable analogies (e.g., comparing a three-tier architecture to a restaurant's front-of-house and kitchen) to ensure clients understand the system structure.
  • Stakeholder Review Meetings: Generate clear justifications for technical stack choices by focusing on business outcomes, such as data reliability and performance, rather than just technical specifications.
  • User Acceptance Testing (UAT) Preparation: Provide non-technical users with a simplified overview of data movement and system logic to set the right context before they begin formal testing and sign-off.
nameclient-arch-explain
description生成客户友好的架构说明(通俗语言解释架构层次、数据流、技术选型),适合演示和评审会议。当准备客户演示或用户验收前使用。
stageDESIGN
level_supported[L1, L2, L3]

client-arch-explain: 客户友好的架构说明

描述

生成客户友好的架构说明(通俗语言解释架构层次、数据流、技术选型),适合演示和评审会议。

适用场景

  • WORKFLOW:准备客户演示或评审会议
  • 沟通场景:需要向非技术人员解释架构
  • 用户验收前:生成客户友好的沟通材料

输入

  • design/ 目录(ARCH/VS/SD/DM)
  • requirements/ 目录(业务上下文)

输出

  • 客户友好的架构说明(markdown)
  • 架构概览(1-2 段通俗语言)
  • 分层说明(每层 1-2 句业务价值)
  • 数据流说明(结合业务场景)
  • 技术选型说明(业务语言)

执行策略

  1. 从 ARCH 提取架构层次
  2. 从 VS 提取核心业务场景
  3. 从 SD 提取数据流
  4. 生成客户友好的架构说明:
    • 架构概览:用类比(如"三层结构类似商店的前台、仓库、财务")
    • 分层说明:每层的业务价值(如"展示层负责用户看到的界面")
    • 数��流说明:结合业务场景(如"当用户提交订单时,数据从前台流向仓库")
    • 技术选型:业务语言(如"PostgreSQL确保订单数据不会丢失")
  5. 确保业务语言占比 ≥90%

价值

  • SPEC 组织:补充客户沟通材料
  • PM/用户:理解架构设计
  • Dev:清晰的业务上下文