Deepchat Sdd
Use before substantial DeepChat code, configuration, documentation, test, build...
Install
npx skills add ThinkInAIXYZ/deepchat --skill deepchat-sdd -g -a claude-code -y- Repository
- ThinkInAIXYZ/deepchat6.4k
- Category
- Testing
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 2,052 tokens
- Runs scripts
- No, instructions only
What it does
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.
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 folders. Keep current architecture reference docs such as docs/architecture/agent-system.md in place; use subfolders for new architecture targets.
Treat a bug as SDD-worthy only when the root cause, blast radius, or fix path is complex enough that
future developers benefit from the written record. For simple style defects or obvious local logic
fixes, skip docs/issues/* and implement directly.
If a bug fix introduces a new user-visible capability, data migration, public contract, or cross-module redesign, classify the work as feature or architecture instead.
Required Artifacts
Feature and architecture goals use two artifacts:
