What problem does it solve?
Substantial changes to the DeepChat codebase often lack a durable decision record and a clear execution path, making it hard for future developers to understand why and how work was done. This Skill enforces a spec-driven development (SDD) workflow that produces RFC-style specs and ordered implementation plans before code changes begin.
Core Features & Use Cases
- Goal Classification: Routes work into docs/features, docs/issues, or docs/architecture folders based on whether it is a new capability, complex bug, or refactor.
- RFC and Plan Artifacts: Generates a normative spec.md covering design, invariants, and acceptance criteria, plus plan.md as the single ordered implementation tracker.
- Implementation-First Validation: Completes planned implementation before deciding on new tests, then selects the smallest useful validation and runs format, i18n, lint, and typecheck gates.
- Use Case: When adding a new MCP integration to DeepChat, use this Skill to write an RFC in docs/features, track implementation slices in plan.md, and optionally sync a labeled GitHub issue after approval.
Quick Start
Use the deepchat-sdd skill to plan and document my new DeepChat feature before writing any code.