Claude Skill

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 when a lin

LLM Mart · 0 points · 9 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download thinkinaixyz-deepchat-.agents_skills_deepchat-sdd-cleanup-f886d6e.zip · 1 KB

thinkinaixyz/deepchat 6332 735 forks Apache-2.0 Updated 7d ago

Part of thinkinaixyz/deepchat — 22 skills

Install

skills CLI npx skills add https://github.com/ThinkInAIXYZ/deepchat/tree/dev/.agents/skills/deepchat-sdd-cleanup

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install thinkinaixyz-deepchat@llmmart

Git git clone https://github.com/ThinkInAIXYZ/deepchat.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole thinkinaixyz/deepchat collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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

Inspect docs/spec-driven-dev.md, docs/README.md, and git status.
Inventory docs/features, docs/issues, and docs/architecture with find or rg.
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
Apply only changes with clear evidence. Keep a concise keep/delete/update list for handoff.
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.

Files (deepchat)

agents

openai.yaml 252 B

interface:
  display_name: "DeepChat SDD Cleanup"
  short_description: "Prune stale DeepChat SDD documentation"
  default_prompt: "Use $deepchat-sdd-cleanup only when the developer explicitly asks to clean, prune, tidy, or organize DeepChat SDD docs."

SKILL.md 3.1 KB

---
name: deepchat-sdd-cleanup
description: 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 when a linked GitHub issue is closed or implementation and validation evidence proves the bug no longer exists, drops stale plans and legacy task files from completed feature or architecture goals, and deletes obsolete feature or architecture docs.
---

# 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.