Use only when a developer explicitly asks to clean, prune, tidy, or organize DeepChat SDD documentation after implementation and validation. Scans docs/features, docs/issues, and docs/architecture; prefers multi-agent review when available; removes completed issue docs when a linked GitHub issue is closed or implementation and validation evidence proves the bug no longer exists, drops stale plans and legacy task files from completed feature or architecture goals, and deletes obsolete feature or architecture docs.
deepchat-sdd
deepchat-sdd is an open-source docs skill for Claude Code and compatible agents, published by ThinkInAIXYZ. Its author describes it as: “Use before substantial DeepChat code, configuration, documentation, test, build, feature, issue, refactor, or architecture changes that need a durable RFC and an explicit execution path. Skip trivial style fixes, smal…”. The project has 6.2k stars on GitHub and is available under the Apache-2.0 license. Add it to your setup with `git clone https://github.com/ThinkInAIXYZ/deepchat ~/.claude/skills/deepchat-sdd`.
What deepchat-sdd does
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.
Installation
Add deepchat-sdd to your agent with:
git clone https://github.com/ThinkInAIXYZ/deepchat ~/.claude/skills/deepchat-sddAlways review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.
What's inside
The SKILL.md for deepchat-sdd is organised into these sections:
- When To Use
- Classify The Goal
- Required Artifacts
- Artifact Boundaries
- GitHub Issue Sync
- Workflow
- Implementation-First Validation
- Documentation Hygiene
When to use it
Reach for deepchat-sdd when you want docs help from your agent without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.
Strengths
- Clear Apache-2.0 license — safe to read and adapt
- Ships in ThinkInAIXYZ/deepchat, an established project with 6,228 GitHub stars
- Actively maintained (recent commits)
Topics
Frequently asked questions
- What does deepchat-sdd do?
- Use before substantial DeepChat code, configuration, documentation, test, build, feature, issue, refactor, or architecture changes that need a durable RFC and an explicit execution path. Skip trivial style fixes, small localized logic changes, routine docs edits, and simple bugs unless the developer asks for SDD. Use plan.md as the only separate tracker when needed, default to implementation-first validation, and ask before optional GitHub issue sync unless the developer explicitly requested sync.
- How do I install deepchat-sdd?
- Run git clone https://github.com/ThinkInAIXYZ/deepchat ~/.claude/skills/deepchat-sdd in your agent, then reload your skills. Review the source at https://github.com/ThinkInAIXYZ/deepchat before installing.
- Is deepchat-sdd free to use?
- Yes. deepchat-sdd is free and open source under the Apache-2.0 license, so you can read, run, and adapt it within that license's terms.
- Where does deepchat-sdd come from?
- deepchat-sdd ships inside ThinkInAIXYZ/deepchat, a repository that contains 25 catalogued skills in total. The repository's 6,228 GitHub stars apply to that whole collection, not to this skill on its own.
Related skills
More Docs →Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks
Diagnose LazyCodex and Codex CLI installation health against the latest sources. Use whenever the user asks for a doctor or health check, says LazyCodex, lazycodex-ai, omo-codex, or Codex behaves oddly after an install, update, or config change, suspects a stale, drifted, or broken setup, or wants the local install audited and compared with the latest LazyCodex and Codex code.
Yao process documentation expert. ALWAYS invoke this skill when the user needs to discover available processes, read process signatures, or validate process names. Do not guess process APIs — use this skill first.