---
name: DeepChat SDD Cleanup
slug: deepchat-sdd-cleanup
category: Quality
description: DeepChat SDD Cleanup scans docs/features, docs/issues, and docs/architecture to remove completed issue docs, stale plans, and obsolete specs when a developer explicitly asks for cleanup or tidying. It uses multi-agent review and validates references before deleting files.
github: "https://github.com/ThinkInAIXYZ/deepchat/tree/dev/.agents/skills/deepchat-sdd-cleanup"
language: TypeScript
stars: 6222
forks: 716
install: "npx degit https://github.com/ThinkInAIXYZ/deepchat/tree/dev/.agents/skills/deepchat-sdd-cleanup ~/.claude/skills/deepchat-sdd-cleanup"
installs_to: ~/.claude/skills/deepchat-sdd-cleanup
source_path: .agents/skills/deepchat-sdd-cleanup/SKILL.md
collection_size: 24
category_size: 1354
collection_url: "https://dirskills.com/collections/ThinkInAIXYZ/deepchat"
added: 2026-08-15T06:52:08.969Z
last_synced: 2026-08-15T06:52:08.969Z
canonical_url: "https://dirskills.com/skills/deepchat-sdd-cleanup"
---

# DeepChat SDD Cleanup

DeepChat SDD Cleanup scans docs/features, docs/issues, and docs/architecture to remove completed issue docs, stale plans, and obsolete specs when a developer explicitly asks for cleanup or tidying. It uses multi-agent review and validates references before deleting files.

**Install:**

```bash
npx degit https://github.com/ThinkInAIXYZ/deepchat/tree/dev/.agents/skills/deepchat-sdd-cleanup ~/.claude/skills/deepchat-sdd-cleanup
```

## README

# 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 any legacy `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
  implementation and validation evidence prove the bug no longer exists.
- Removed feature: delete its folder when the product/code path is gone and the spec has no reusable
  decision record.
- Obsolete architecture: delete its folder when the module was fully replaced and the doc no longer
  describes a maintained boundary; otherwise update the spec.
- Historical feature spec affected by an architecture refactor: update the retained spec instead of
  leaving contradictory docs.

## GitHub Checks

Use `gh` only when it is installed and authenticated. For linked issue docs, verify closure with
`gh issue view <number> --json state,url,title` when possible. If `gh` is unavailable, do not delete
solely because a GitHub link looks old.

## Never Delete

- Active work with unchecked `plan.md` steps or legacy tasks.
- Any document containing unresolved `[NEEDS CLARIFICATION]`.
- A document referenced by `docs/README.md`, `docs/ARCHITECTURE.md`, `docs/FLOWS.md`, or AGENTS
  instructions unless the reference is updated in the same change.
- Runtime baselines or machine-read files unless the cleanup request explicitly covers them.

## Validation

- Run `rg -n "plan.md|tasks.md|docs/archives|NEEDS CLARIFICATION" docs AGENTS.md .agents/skills`
  and inspect any stale policy references.
- Run `git status --short`.
- For Markdown-only cleanup, formatting/lint commands are optional unless repository instructions or
  touched generated files require them.