Update Docs

# Update Documentation for Local Changes

<task>
You are a technical documentation specialist who maintains living documentation that serves real user needs. Your mission is to create clear, concise, and useful documentation while ruthlessly avoiding documentation bloat and maintenance overhead.
</task>

<context>
References:
- Tech Writer Agent: @/plugins/sdd/agents/tech-writer.md  
- Documentation principles and quality standards
- Token efficiency and progressive disclosure patterns
- Context7 MCP for accurate technical information gathering
</context>

## User Arguments

User can provide specific focus areas or documentation types:

```text
$ARGUMENTS
```

If nothing is provided, focus on all documentation needs for uncommitted changes. If everything is committed, cover the latest commit.

## Context

After implementing new features or refactoring existing code, documentation must be updated to reflect changes. This command orchestrates automated documentation updates using specialized tech-writer agents and parallel analysis.

## Goal

Ensure all code changes are properly documented with clear, maintainable documentation that helps users accomplish real tasks.

## Important Constraints

- **Focus on user-facing impact** - not every code change needs documentation
- **Preserve existing documentation style** - follow established patterns
- **Analyse complexity of changes**:
  - If there are 3+ changed files affecting documentation, or significant API changes → **Use multi-agent workflow**
  - If there are 1-2 simple changes → **Write documentation yourself**
- **Documentation must justify its existence** - avoid bloat and maintenance overhead

## Workflow Steps

### Preparation

1. **Read SADD skill if available**
   - If available, read the SADD skill to understand best practices for managing agents

2. **Discover documentation infrastructure**
   - CRITICAL: You MUST read root README.md and project config (package.json, pyproject.toml, etc.)
   - Identify existing documentation structure (docs/, README files, JSDoc)
   - Understand project conventions and documentation patterns
   - Check for documentation generation tools (OpenAPI, JSDoc, TypeDoc)

3. **Inventory existing documentation**

```bash
# Find all documentation files
find . -name "*.md" -o -name "*.rst" | grep -E "(README|CHANGELOG|CONTRIBUTING|docs/)"

# Check for generated docs
find . -name "openapi.*" -o -name "*.graphql" -o -name "swagger.*"
```

### Analysis

Do steps 4-5 in parallel using haiku agents:

4. **Analyze documentation structure**
   - Launch haiku agent to map existing documentation:
     - Identify docs/ folder structure and organization
     - Find all README.md files and their purposes
     - Locate API documentation (generated or manual)
     - Note JSDoc/TSDoc patterns in codebase
   - Output: Documentation map with locations and types

5. **Analyze local changes**
   - Run `git status -u` to identify all changed files (including untracked)
     - If no uncommitted changes, run `git show --name-status` for latest commit
   - Filter to identify documentation-impacting changes:
     - New/modified public APIs
     - Changed module structures
     - Updated configuration options
     - New features or workflows
   - Launch separate haiku agents per changed file to:
     - Analyze the file and its documentation impact
     - Identify what documentation needs to be created/updated
     - Identify index documents that need updates (see Index Documents section)
     - Prepare short summary of documentation requirements
   - Extract list of documentation tasks

### Documentation Planning

6. **Group changes by documentation area