docs-synclisted
Install: claude install-skill rterakedis/leanwheel-skills
# Docs Sync Skill
Composable doc-maintenance ops. The caller supplies the trigger and context; this skill owns the *how* (DD-24). Every op is gated and idempotent — it does nothing when there's nothing to update.
**Model routing.** OPERATIONAL and PROMOTE are mechanical, diff-grounded prose and run on the cheapest model: callers spawn the `lw-docs-sync` subagent (pinned to Haiku) via a literal Agent tool call — `subagent_type: "lw-docs-sync"`, prompt naming the op (`OPERATIONAL` / `PROMOTE`) and its input (story path / changed-file list / epic number) — rather than running inline:
- The **orchestrator** owns the spawn — `lw-story-developer` does not run doc-sync inline (it can't spawn a child anyway). story-/epic-flywheel spawn after the dev phase returns (OPERATIONAL, story path) and at the epic boundary / retrospective (PROMOTE, epic number).
- Main-session callers (`quick-dev`, standalone `dev-story`, direct `/docs-sync`) spawn likewise.
- **DRIFT is the exception** — a one-line advisory, so it stays inline in the caller.
Fallback when no spawn is possible: run the op inline.
**Three doc audiences, deliberately separated:**
- **Human operational guides** — `docs/setup/` (stand up from scratch), `docs/maintainer/` (operate it / how it works), `docs/sql/` (database). Each area is a hub `index.md` plus focused topical pages. Maintained and grown by **OPERATIONAL**.
- **LLM planning doc** — `docs/architecture.md` (read by `/create-story`, `/epics`, `/check-readiness`). Fed