docslisted

# Docs Keep `./docs/` honest. Scout the code, diff it against what the docs claim, write what's true. Small canonical set - easy to keep current, hard to let rot. ## What this skill is - and isn't | Skill | Question it answers | Output | |---|---|---| | `vd:scout` | "Where does X live in this repo?" | File map, no writes | | `vd:journal` | "What did *I* just learn / decide / break?" | Personal entry in the injected Journals path | | **`vd:docs`** | **"Are the shared `./docs/` files true and current?"** | **Updated files in `./docs/`** | `./docs/` is **team-facing** truth. Journals are personal. Plans/reports live under `./plans/`. Changelog, roadmap, and PR-style narrative are intentionally **not** in this skill's scope - those rot fastest and `vd:ship` / `vd:journal` already cover them. ## Subcommands | Subcommand | Reference | When | |---|---|---| | `init` | `references/init-workflow.md` | Fresh repo - no `./docs/` yet, or only a stub README | | `update` | `references/update-workflow.md` | Code drifted from docs after a feature, refactor, or migration | | `check` | `references/check-workflow.md` | Validate-only: required files, size, freshness, broken refs. No writes. | | `adr` | `references/adr-workflow.md` | Record an architecture decision (the *why* behind an irreversible choice) under `docs/decisions/` | Parse `$ARGUMENTS` first word (in runtimes without `$ARGUMENTS` substitution, use the text following the skill name in the user's message): - `init` / `update` /