atomic-documentationlisted

<trigger> Auto-fires on: "doc this change", "what surfaces does this touch", "doc impact for this diff", "what needs documenting". Also invoked by `/documentation` (authoring mode) and by ship verbs (maintenance mode, between stage and signals). </trigger> This skill reads the project's indexed documentation surfaces, matches a diff against them, and either flags stale/incomplete docs (maintenance mode) or runs the full discovery + generation pipeline (authoring mode). It emits a structured YAML block listing affected surfaces. When the user picks "Yes", it opens the file and makes the edit. ## Two voices | Voice | Where | Style | |-------|-------|-------| | **How Claude talks** | TUI replies | Atomic output style: terse, fragments OK, drop articles. Governed by `output-styles/atomic.md`. | | **How files are written** | All file content | Narrative docs (`README.md`, `docs/guides/`) use `atomic-prose` skill. Everything else (specs, designs, `CLAUDE.md`, signals, agents, commands) uses terse technical prose: tables, bullets, imperative. | ## How surface routing works The skill reads the `## Documentation surfaces` table from the project's CLAUDE instructions. Search order: `claude.local.md` or `CLAUDE.local.md` (treated as a pair) → `CLAUDE.md`. First file containing the heading wins. Expected table format: ```markdown ## Documentation surfaces | Path | Covers | Voice | |------|--------|-------| | `docs/architecture/payments.md` | billing, webhooks, Stripe | atomic-