jarvis-doc-author

# Jarvis Doc Author When a Jarvis doc is written, the rule is: **classify first, then structure, then phrase, then self-check.** Not the other way around. This skill provides the scaffolding. It does not replace thinking — it enforces the discipline that separates a pile of internal Markdown files from a *real* doc layer (role models: Kubernetes doc site, Docker manuals, GitHub Docs). ## When to trigger Activate this skill when the user (via voice or chat) or a Sub-Jarvis explicitly or implicitly wants to write a **new doc** or **structurally** rework an existing doc. Concrete examples: - "Schreib ein Doc ueber den BrainManager-Routing-Discipline-Mechanismus." (Write a doc about the BrainManager routing discipline mechanism.) - "Leg ein ADR an fuer die Sub-Jarvis-Hard-Cap-Entscheidung." (Create an ADR for the Sub-Jarvis hard-cap decision.) - "Dokumentiere wie man einen neuen Brain-Provider hinzufuegt." (Document how to add a new brain provider.) - "Fass die Phase-6-Ergebnisse als Test-Report zusammen." (Summarize the Phase 6 results as a test report.) - "Mach mir eine How-To fuer das Voice-Bridge-Setup." (Create a how-to for the voice-bridge setup.) - A Sub-Jarvis receives the task from the main Jarvis "schreib das in ``docs/...`` rein" (write this into ``docs/...``) — then the Sub-Jarvis consults this skill before writing. Do NOT trigger on: - Code comments, docstrings, type hints — those follow the CLAUDE.md rule (code identifiers in English), but need no doc s...