deepchat-sdd
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.
npx skills add ThinkInAIXYZ/deepchat --skill deepchat-sdd --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 The Goal Create one kebab-case folder per goal: - New capability, user-visible behavior, integration, or tool large enough to need a shared plan: `docs/features/<goal>/` - Complex bug, regression, failing test, CI failure, reliability problem, or prompt/runtime issue: `docs/issues/<goal>/` - Refactor, migration, dependency boundary, shared contract, runtime architecture, or cross-module design: `docs/architecture/<goal>/` If one request contains multiple independent goals, split them into separate folde
- When To Use
- Classify The Goal
- Required Artifacts
- GitHub Issue Sync
- Workflow
- Documentation Hygiene
What does the deepchat-sdd skill do?
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.
How do I install it?
Run `npx skills add ThinkInAIXYZ/deepchat --skill deepchat-sdd --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ThinkInAIXYZ/deepchat, a repository with 6,191 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.