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.