deepchat-sdd

仓库创建 2025年2月14日最近提交 5 小时前SkillHot 收录 20 天前

▸ 精选理由

引导以规范化规格驱动开发，降低设计散乱与回归风险，适合团队协作。

这个 Skill 做什么

在变更前创建或更新 DeepChat 的规范化 SDD（功能/缺陷/架构）。

在做重大 DeepChat 代码、配置、功能、测试或架构改动前，撰写或更新结构化的 SDD（功能规范、复杂缺陷说明或架构决策），为多人协作保留可追溯的设计记录。小幅样式改动或微小 bug 修复一般可以跳过，除非开发者特别要求。特点是把重要变更分类并在必要时询问是否同步到 GitHub issue。

▸ 展开 SKILL.md 英文原文

Use before substantial DeepChat code, configuration, documentation, test, build, feature, issue, refactor, or architecture changes that need a durable spec. Skip trivial style fixes, small localized logic changes, routine docs edits, and simple bugs unless the developer asks for SDD. Classify substantial work into feature SDD, complex-bug issue spec, or architecture SDD; ask before optional GitHub issue sync unless the developer explicitly requested sync.

Skill 开发管理需求规范SDD项目流程通用

6.2k

Stars

707

Forks

仓库内 Skill

+70

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/ThinkInAIXYZ/deepchat/dev/.agents/skills/deepchat-sdd/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/ThinkInAIXYZ/deepchat/dev/.agents/skills/deepchat-sdd/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# DeepChat SDD

## When To Use

Use this skill before substantial DeepChat source code, configuration, tests, docs, build
scripts, release workflows, or project structure changes that need shared context or a durable
decision record.

Skip SDD for trivial or tightly localized work unless the developer explicitly asks for it:

- visual/style fixes, copy changes, and small UI layout adjustments
- simple localized logic changes with a clear owner module
- routine docs edits that do not change project direction
- release metadata already covered by the release flow

If the scope is unclear, inspect first and then ask whether SDD is wanted instead of creating
artifacts by default.

## Classify Th

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有