ThinkInAIXYZ/deepchat / .agents/skills/deepchat-sdd-cleanup
deepchat-sdd-cleanup
VerifiedUse 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.1 KB |
| agents/openai.yaml | config | 252 B |
SKILL.md
View on GitHub---
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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |