deepchat-sdd-cleanup

Prunes stale spec-driven development documentation from DeepChat docs directories.

6.3k|728|Updated Feb 14, 2025
One-click install
npx skills add https://github.com/ThinkInAIXYZ/deepchat --skill deepchat-sdd-cleanup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deepchat-sdd-cleanup
Source: https://github.com/ThinkInAIXYZ/deepchat/tree/main/.agents/skills/deepchat-sdd-cleanup
Command: npx skills add https://github.com/ThinkInAIXYZ/deepchat --skill deepchat-sdd-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec-driven development workflows accumulate stale plans, task lists, and obsolete specs across docs/features, docs/issues, and docs/architecture, making it hard to tell which documents still reflect maintained behavior.

Core Features & Use Cases

  • Evidence-Based Deletion: Removes completed issue docs only when a linked GitHub issue is closed or implementation and validation evidence proves the bug no longer exists.
  • Multi-Agent Review: Prefers parallel sub-agent passes over docs/features, docs/issues, and docs/architecture, plus an optional verifier pass over proposed deletions.
  • Safety Guardrails: Never deletes active work with unchecked plan steps, unresolved [NEEDS CLARIFICATION] markers, or documents referenced by docs/README.md, docs/ARCHITECTURE.md, docs/FLOWS.md, or AGENTS instructions.
  • Use Case: After shipping several features and closing bug issues, ask the agent to tidy the SDD docs; it inventories the directories, verifies GitHub issue states with gh, deletes stale plans and legacy tasks, and validates remaining references with rg.

Quick Start

Ask the agent to clean up and prune stale DeepChat SDD documentation in docs/features, docs/issues, and docs/architecture.

Frequently Asked Questions about deepchat-sdd-cleanup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clean up stale spec-driven development docs in DeepChat?

Explicitly ask the agent to clean, prune, or tidy the SDD documentation. It inventories docs/features, docs/issues, and docs/architecture, reviews them with parallel sub-agent passes when available, and deletes only files backed by clear completion evidence.

When does the skill delete a completed issue document?

An issue folder is deleted only when the linked GitHub issue is closed, verified with gh issue view when the CLI is available, or when implementation and validation evidence proves the bug no longer exists.

Can SDD cleanup run automatically after feature work?

No. The skill runs only when the developer explicitly requests documentation cleanup, tidying, or pruning. It is not an automatic final step of feature, bug, architecture, or release work.

What documents are never deleted during SDD cleanup?

Active work with unchecked plan steps, documents containing unresolved [NEEDS CLARIFICATION] markers, files referenced by docs/README.md, docs/ARCHITECTURE.md, docs/FLOWS.md, or AGENTS instructions, and runtime baselines are always preserved.

What happens if the GitHub CLI is not installed?

If gh is unavailable or unauthenticated, the skill skips GitHub state verification and will not delete a document solely because a linked GitHub issue looks old. Deletion then requires local implementation and validation evidence.