Deepchat Sdd

It makes you classify whether you're building a feature, fixing an issue, or refactoring architecture, then generates three markdown files in the right docs folder: spec.md for requirements, plan.md for approach, and tasks.md for execution. Every NEEDS CLARIFICATION marker must be resolved before implementation starts. The workflow is opinionated about DeepChat's patterns like Presenter boundaries and typed contracts, and it includes hygiene rules for archiving stale specs. If you're working on DeepChat or want to enforce similar discipline on your own Electron project, this keeps design decisions visible and prevents diving straight into code when you should be writing things down first.