Document Optimization

Analyze project documentation for optimization opportunities.

Objectives

1. Detect redundancy: Find hand-written docs that duplicate auto-generated content
2. Find outdated content: Identify docs that haven't been updated
3. Suggest cleanup: Recommend file moves, deletions, and consolidations

Analysis Strategy

Phase 1: Identify Auto-Generated Docs

Scan for docs that can be regenerated:

• PROJECT_INDEX.md - regenerate via /airis:index-repo
• Other generated files (check for "DO NOT EDIT" markers)

Phase 2: Detect Redundancy

Compare hand-written docs against auto-generated ones:

IF (hand-written doc content overlaps with auto-generated):
  → Suggest deletion (auto-generated is always fresh)

Phase 3: File Organization

Check naming conventions and placement:

• Config files: lowercase (manifest.toml, justfile)
• Important docs: uppercase (README.md, CLAUDE.md)
• Utility files: move to appropriate dirs (dependency-cruiser.cjs → tools/)

Phase 4: Content Analysis

Examine doc freshness and relevance:

• Check git log for last update
• Detect outdated references
• Find duplicate sections

Execution

Run comprehensive analysis on current project:

1. List all docs in root and docs/ directory
2. Categorize by type (auto-generated vs hand-written)
3. Analyze content overlap
4. Generate optimization report

Output format:

# Documentation Optimization Report

## Deletion Candidates (Redundant with Auto-Generated)
- `ARCHITECTURE.md` - 80% overlap with `PROJECT_INDEX.md`
  → Can regenerate PROJECT_INDEX.md anytime with `/airis:index-repo`

## Relocation Candidates
- `dependency-cruiser.cjs` → `tools/dependency-cruiser.cjs`

## Consolidation Opportunities
- Content in `AGENTS.md` and `CLAUDE.md` has overlap in [section X]

## Keep (Unique Content)
- `README.md` - Project overview (manual)
- `CLAUDE.md` - LLM instructions (manual)

Proceed with analysis.