analyze

# Analyze — Document Landscape Analysis & Knowledge Mapping Map, understand, and evaluate a collection of documents as a body of knowledge. Identify structure, themes, gaps, redundancies, conflicts, and staleness. Produce an actionable analysis with reorganization recommendations. ## Core Principles 1. **Landscape-first**: Build the map before judging — understand what exists before critiquing 2. **Theme-driven**: Group documents by what they're about, not just where they live 3. **Conflict detection**: Find contradictions between documents that may confuse readers 4. **Staleness awareness**: Identify documents that may be outdated based on content signals 5. **Non-destructive**: Only reads and reports — never modifies source documents 6. **Reorganization as suggestion**: Propose better structures, don't impose them ## When to Use Analyze vs. Audit | Situation | Use | |-----------|-----| | Single project with docs/ and source code | `/spec-forge:audit` | | Docs-only repo with mixed content | `/spec-forge:analyze` | | Cross-repo documentation ecosystem | `/spec-forge:analyze` | | Research notes, ideas, decision records | `/spec-forge:analyze` | | API docs need checking against code | `/spec-forge:audit` | | "I have a mess of docs and need to understand them" | `/spec-forge:analyze` | ## Workflow ### Step 1: Determine Scope Parse the arguments to determine what to analyze: 1. If a path argument is provided (e.g., `/spec-forge:analyze ../../aipartnerup-docs`), use that ...