No useless/outdated files

Severity: Recommended

Check automatically for suspicious patterns:

# Backup/temp files
find . -name "*.bak" -o -name "*.old" -o -name "*.orig" -o -name "*.tmp" 2>/dev/null

# Common junk in root
ls -la TODO.txt notes.txt scratch.* temp.* 2>/dev/null

# Suspicious directories
ls -d old/ backup/ archive/ tmp/ temp/ 2>/dev/null

Check for dated/report markdown files:

# Files with dates in name (2024-01-15-something.md)
find . -name "*.md" | grep -E "[0-9]{4}-[0-9]{2}-[0-9]{2}"

# Report-style files
find . -name "*.md" | grep -iE "(report|meeting|notes|standup|retro|review)"

Check for outdated planning documents:

# Planning/spec directories
ls -d docs/specs/ docs/planning/ docs/plans/ docs/rfcs/ specs/ planning/ 2>/dev/null

# Common planning file patterns
find . -name "*.md" | xargs grep -l -iE "(RFC|proposal|spec|roadmap|plan)" 2>/dev/null

# Check modification dates - flag if not touched in 6+ months

Pass criteria:

• No obviously outdated or unused files
• No backup directories committed
• No dated reports/meeting notes committed
• Planning docs are current or removed
• User confirms any flagged files are intentional

Fail criteria:

• .bak, .old, .orig files committed
• backup/, old/, archive/ directories in repo
• Dated markdown files (meeting notes, reports) in repo
• Outdated specs/RFCs that don't match implementation
• Clearly abandoned files

If suspicious files found, ask user: "These files may be outdated: [list]. Should they be removed or are they intentionally kept?"

Evidence to capture:

• List of flagged files by category
• User justification for any kept files

---