deepchat-sdd-cleanup
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 tied to closed GitHub issues, drops stale plan/tasks files from completed feature or architecture goals, and deletes obsolete feature or architecture docs.
npx skills add ThinkInAIXYZ/deepchat --skill deepchat-sdd-cleanup --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 Cleanup ## Rule Run this skill only when the developer explicitly asks for SDD cleanup, documentation tidying, pruning, or removal of completed/stale SDD files. Do not run it as an automatic final step of ordinary feature, bug, architecture, or release work. ## Workflow 1. Inspect `docs/spec-driven-dev.md`, `docs/README.md`, and `git status`. 2. Inventory `docs/features`, `docs/issues`, and `docs/architecture` with `find` or `rg`. 3. Prefer parallel sub-agent review when available: - one pass for `docs/features` - one pass for `docs/issues` - one pass for `docs/architecture` - optional verifier pass over proposed deletes 4. Apply only changes with clear evidence. Keep a concise keep/delete/update list for handoff. 5. Validate references after edits. ## Cleanup Rules - Completed feature or architecture goal: delete `plan.md` and `tasks.md`; keep `spec.md` only when it still defines a maintained contract, regression guard, platform policy, or architecture decision. - Completed issue goal: delete the issue folder when a linked GitHub issue is closed or the local code and tests prove the bug no longer exists. - Removed feature: delete its folder when the product/code pat
- Rule
- Workflow
- Cleanup Rules
- GitHub Checks
- Never Delete
- Validation
What does the deepchat-sdd-cleanup skill do?
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 tied to closed GitHub issues, drops stale plan/tasks files from completed feature or architecture goals, and deletes obsolete feature or architecture docs.
How do I install it?
Run `npx skills add ThinkInAIXYZ/deepchat --skill deepchat-sdd-cleanup --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.