dsh-deep-research
Skill79 starsChanged 13 days agoMITView on GitHub
深度技术方案调研、多维竞品对比与架构选型专家。支持 10+ 维度 Trade-off 决策矩阵输出、大厂标准 RFC/ADR 架构提案白皮书撰写,并在交付时提供严密的可视化选型决策推导树与架构决策工作留痕卡片。
In this repository26 other files it gives its agents.
- doc-tidySkill
- dsh-backupSkill
- dsh-claude-styleSkill
- dsh-code-craftSkill
- dsh-crewSkill
- dsh-data-craftSkill
- dsh-diagramSkill
- dsh-doc-publisherSkill
- dsh-doc-searchSkill
- dsh-doc-tidySkill
- dsh-excel-copilotSkill
- dsh-flashgouSkill
- dsh-lifeSkill
- dsh-mail-craftSkill
- dsh-meeting-copilotSkill
- dsh-memory-syncSkill
- dsh-mobileSkill
- dsh-reviewSkill
- dsh-scrum-masterSkill
- dsh-slidesSkill
- dsh-storyboardSkill
- dsh-tierSkill
- dsh-videoSkill
- dsh-voiceSkill
- dsh-web-crawlerSkill
- dsh-write-craftSkill
The file
Files
深度技术调研与架构选型技能 (dsh-deep-research)
当面临重大的技术方案决策、中间件/数据库选型、竞品技术方案对标或撰写系统架构提案时,本技能提供严谨、系统、工业级的决策支撑,严格遵循可视化推导树与 ADR 架构留痕规范。
🧭 可视化选型决策推导树 (Decision Workflow)
每次执行技术方案调研时,首先在回答中呈现标准的选型推导图:
flowchart TD
classDef req fill:#161b22,stroke:#58a6ff,stroke-width:2px,color:#f0f6fc;
classDef matrix fill:#21262d,stroke:#bc8cff,stroke-width:2px,color:#f0f6fc;
classDef decide fill:#21262d,stroke:#3fb950,stroke-width:2px,color:#f0f6fc;
classDef adr fill:#21262d,stroke:#d29922,stroke-width:2px,color:#f0f6fc;
Demand["🎯 核心业务场景与硬性约束 (QPS/成本/SLA)"]:::req --> Matrix["📊 10 维选型决策权衡矩阵 (Trade-off Matrix)"]:::matrix
Matrix --> Dim1["读写吞吐 & 延迟 P99"]
Matrix --> Dim2["运维与硬件成本 (TCO)"]
Matrix --> Dim3["生态成熟度 & 社区活跃度"]
Matrix --> Dim4["高可用与容灾恢复难度"]
Dim1 & Dim2 & Dim3 & Dim4 --> Filter["⚖️ 关键约束筛选与边界权衡"]:::matrix
Filter --> Choice["🏆 最终推荐方案与决策理由"]:::decide
Choice --> ADR["📋 归档架构决策记录 (ADR / RFC 留痕)"]:::adr🛠️ 核心交付规范
1. 10 维技术权衡矩阵 (Trade-off Matrix)
必须对候选方案(如方案 A vs 方案 B vs 方案 C)建立严密的对比表格:
- 核心维度清单:
- 架构复杂度与数据一致性模型 (CAP / BASE)
- 读写性能与并发极限 (QPS / TPS / Latency P99)
- 硬件资源占用与服务器成本 (TCO)
- 生态插件、客户端 SDK 丰富度
- 运维监控难度与灾备恢复成本
- 数据迁移与向后扩展性 (Sharding / Rebalance)
- 团队技术栈学习曲线
- 开源协议商用友好度 (MIT / Apache 2.0 / LGPL / AGPL)
- 已知线上严重坑点与社区活跃度
- 综合推荐度评级 (⭐⭐⭐⭐⭐)
2. 标准大厂 RFC / ADR 架构提案
- Context (背景与痛点):为什么现在需要做这个选型?
- Decision (最终决策):明确选择哪个方案,版本是多少?
- Consequences (利弊影响):采用该方案带来的正面收益(Positive)与负面代价(Negative/Trade-offs);
- Rollback & Migration (迁移与回滚预案):灰度放量计划、降级开关与极端情况回滚方案。
📋 必带架构决策留痕卡片 (ADR Card)
在交付物末尾,必须输出标准化的 ADR 架构决策留痕卡片:
---
### 📑 架构决策留痕卡片 (Architecture Decision Record - ADR)
- **ADR 编号**:`ADR-20261007-003`
- **方案主题**:`千万级实时日志检索与监控系统存储选型`
- **状态 (Status)**:`✅ Accepted (已采纳)`
- **决策结论**:推荐采用 `ClickHouse + Vector` 架构替代原有 `ELK` 方案。
- **关键考量 (Key Trade-offs)**:
1. 存储成本直降 65%(ClickHouse 列式压缩比可达 5:1~8:1);
2. 聚合分析查询提速 10 倍以上;
3. 放弃高频点查倒排全文打分,换取超高吞吐与极低硬件开销。
- **决策归档时间**:2026-10-07 18:45 (DSH Deep Research Engine)
---Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

