doc-tidylisted

Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md). Scan the repo for scattered documentation files, analyze organization issues, and output cleanup recommendations. Analysis only — no changes made. ## Execution Steps ### 1. Full Scan Dispatch 3 parallel Explore subagents (model: haiku) to collect a documentation inventory: **Subagent A — Root + Docs/** - All .md files in root directory (except CLAUDE.md, AGENTS.md) - All files and directory structure under Docs/ (recursive) - For each file: path, first line content, line count **Subagent B — In-code documentation under Assets/** - All .md files under Assets/ (recursive) - Including README, ARCHITECTURE, API_REFERENCE, CHANGELOG, AGENTS.md, etc. - For each file: path, first line content, line count **Subagent C — Config & tool documentation** - .claude/ directory structure - Documentation under scripts/ - Templates under .github/ - Root config files (.mcp.json, opencode.json, etc.) ### 2. Classify Categorize all documents by: | Category | Description | |----------|-------------| | **Long-term design** | System architecture, module design, data config (should be centrally managed) | | **In-code docs** | README, API reference, dev guides (should live with the code) | | **Branch artifacts** | Review outputs, spec files, timelines (should be archived after merge) | | **Temporary files** | tmp-*, one-off bug reports, old prompts (should be clean