documentation-manager

# Documentation Manager Helps decide where to document things and maintain consistency across Pynchy docs. ## Style Guide - Write for a **user trying to achieve a goal**. Don't chronicle the evolution of the codebase. Don't go into unnecessary technical details that are not relevant to the user's goal. - Follow the [Google Style Guide](https://developers.google.com/style). Write in the present tense. Don't use "we" or "they". Write in the active voice. Don't use "is" or "are". - Read `docs/contributing/contributing-docs.md` for the full documentation philosophy and information architecture rules. ## Where to Document What Quick decision tree: **New feature?** - Architecture decision → `docs/architecture/` (find the relevant topic file, or create a new one) - Installation requirement → `docs/install.md` - Security implication → `docs/architecture/security.md` - Development workflow change → `.claude/skills/pynchy-dev/SKILL.md` **Bug fix?** - If it needs install change → `docs/install.md` - Usually: No doc update needed **Refactoring?** - If user-visible → Update relevant docs - If internal only → No doc update ## File Purposes | File | What Goes There | |------|-----------------| | `README.md` | Philosophy, quick start, high-level overview | | `docs/install.md` | Complete installation guide | | `docs/architecture/security.md` | Security model, threat analysis | | `docs/architecture/index.md` | Architecture overview and links to topic pages | | `docs/architecture/*.md...