docs-orchestrator

# Docs Orchestrator Skill > Project-instruction file resolution: CLAUDE.md and AGENTS.md (Codex CLI) are transparent aliases — see [skills/_shared/instruction-file-resolution.md](../_shared/instruction-file-resolution.md). docs-orchestrator coordinates the full documentation lifecycle inside a session: it detects which audiences (User, Dev, Vault) are touched by the agreed scope, generates audience-specific task definitions, threads them into the session-plan pipeline, and verifies that docs tasks produced diffs once waves complete. The skill is opt-in and default-off — when `docs-orchestrator.enabled: false`, all three hook points short-circuit with no output and no cost. docs-orchestrator fills the generative-content gap that sibling skills leave open: `vault-sync` validates but does not write, `vault-mirror` writes metrics-derived `_overview.md` entries but not narratives, `claude-md-drift-check` diagnoses CLAUDE.md (or AGENTS.md on Codex CLI) drift but does not remediate it, and `daily` exclusively owns `03-daily/*`. docs-orchestrator is the only skill that produces new prose grounded in session output. ## Invocation Not user-invocable. Triggered at three hook points within the session lifecycle: 1. **session-start Phase 2.5 "Docs Planning"** — after user alignment, before handing off to session-plan. Reads the agreed scope, runs audience detection (Phase 2 below), and threads the detected audience list into the plan context so session-plan can classify task...