← ClaudeAtlas

auditing-doc-backlogslisted

Use when finished implementation plans or design specs have accumulated anywhere in the tree, when a reader cannot tell which documents describe the built system, or when generated planning documents have piled up over months.
rgant/claude-plugins · ★ 0 · Web & Frontend · score 72
Install: claude install-skill rgant/claude-plugins
# Auditing Doc Backlogs ## Overview A planning document is a tool for building. When the work ships, the code becomes the authority and the document becomes a second, wrong copy of it. **Core principle: keep only what the code cannot say.** A shipped plan in the tree is worse than no document. It reads as current, it names functions that never existed, and a superpowers plan carries `REQUIRED SUB-SKILL: use subagent-driven-development to implement this plan`. That line tells a future agent to rebuild shipped work. ## The Rule ``` PROPOSE EVERY DELETE. DELETE ONLY AFTER THE USER CONFIRMS. ``` You never stage and never commit. The user reviews the working tree and signs the commit. ## Step 0 — Learn the layout and the conventions The repository decides where a document lives and what a living document is called. Learn that before you touch anything. 1. Find the documents. `git ls-files '*.md'` gives the true set. A doc directory sits at the root, next to each project, or next to each library. Do not assume one root `docs/`. 2. Read the repository's own instruction file (`CLAUDE.md`, `AGENTS.md`, `CONTRIBUTING.md`) for a rule about where a document goes. 3. Name the living documents each project already uses. One repository uses `README.md` alone. Another adds an architecture document, a status document, or an operator runbook. 4. Note which of them carry a date in the filename. A date claims the document records one moment. A document that must stay