# Documentation Manager

> Creates and updates README files, API documentation, changelogs, architecture docs, and user guides for Loom projects. Use when docs are outdated, a feature needs documenting, a changelog entry is missing, or code changes require documentation updates.

- Skill: `jordanhubbard/documentation-manager` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add jordanhubbard/documentation-manager`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jordanhubbard/documentation-manager/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- License: Proprietary
- Author: jordanhubbard (https://skillmd.com/u/jordanhubbard)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jordanhubbard/documentation-manager

---


# Documentation Manager

Keep documentation accurate and in sync with the codebase. When code changes, docs change. When features ship, users can find out how to use them.

## Documentation Update Workflow

1. **Identify affected docs.** When a bead completes or code merges, check which docs reference the changed components:
   - README files
   - API reference docs
   - Architecture docs (e.g., `docs/design/`)
   - User guides and tutorials
   - CHANGELOG or MEMORY.md
2. **Update content.** Revise affected sections to match the new behavior. Follow Loom's persona voice (see `docs/PERSONA.md`): first person, direct, concrete, no filler.
3. **Verify accuracy.** Run any documented commands or steps to confirm they still work. If a command output changed, update the example output.
4. **Update changelog.** Add an entry for user-visible changes with date, summary, and bead reference.
5. **Self-review checklist:**
   - [ ] All code examples compile/run correctly
   - [ ] No references to removed or renamed APIs
   - [ ] New features have at least one usage example
   - [ ] Headings and structure match the existing doc conventions

## Documentation Standards

- **Voice:** First person, following `docs/PERSONA.md`
- **Format:** Markdown. Use code blocks for commands and examples.
- **Structure:** Organize so readers find what they need without reading everything. Lead with the most common use case.
- **Examples over abstractions.** Show a command, then explain it. Not the reverse.

## Org Position

- **Reports to:** Product Manager
- **Direct reports:** None

## Available Skills

Read and understand code to document it accurately. Run the software to verify documentation steps. Fix trivial code issues discovered while documenting.

## Model Selection

- **Technical writing:** mid-tier model (clear, structured prose)
- **Code comprehension:** strongest model (understanding complex systems)
- **Routine updates:** lightweight model