# Update-all-docs prompt (Opus 4.8)

A prompt to bring every videoclaw doc back in sync with the current code after a period of
heavy change. Authored with the `prompting-opus-4-8` skill — tuned for Opus 4.8's literal
scope-following (the doc set is enumerated, not sampled), its low default subagent count
(explicit fan-out), and its preference for reasoning over tools (explicit verify-against-code).

Run at **xhigh** effort, and set a large max output budget (start ~64k) so the parallel
subagents have room.

```text
You're working on videoclaw-v3 (the `vclaw` CLI). The codebase has changed a lot recently
and the documentation has drifted. Bring EVERY doc back into sync with the current code.
Documentation accuracy is the goal: every command, flag, artifact, schema, and workflow a
doc describes must match what the code actually does today.

Ground truth is the code, not your memory or the existing prose. The authoritative sources
for what exists are: the COMMANDS array in src/video/cli-schema.ts (and its count assertion
in src/tests/cli-schema.test.ts), `vclaw --help` and per-command `--help` output, the
handlers in src/cli/handlers/, the JSON Schemas in schemas/video/, and the skills in
skills/ with skills/catalog.json. When a doc disagrees with these, the doc is wrong — fix
the doc to match the code (do not change code to match docs).

Scope is ALL of these, not a sample. Update every one that has drifted:
- README.md
- docs/ARCHITECTURE.md, docs/CLI_REFERENCE.md, docs/STUDIO.md, docs/ASSEMBLE.md,
  docs/PRODUCTION_WORKFLOW.md, docs/REVIEW_UI_STORYBOARD_WORKFLOW.md,
  docs/preview-portal-audit.md, docs/STORY_BIBLE.md, docs/DIRECTOR_BLUEPRINT.md,
  docs/MOTION_OVERLAY.md, docs/BRAND_AGENCY.md, docs/REFERENCE_SHEETS.md,
  docs/SCENE_CANDIDATES.md, docs/OPERATIONS.md, docs/GENERATION_TELEMETRY.md,
  docs/OBSIDIAN.md, docs/TEMPLATES.md, docs/MIGRATION.md, docs/DEPRECATION.md,
  docs/RELEASE_READINESS.md, docs/MASTER_PLAN_ALIGNMENT.md, docs/DIAGRAMS_SOURCE.md
- docs/adr/* (architecture decision records — keep decisions intact; only fix factual drift)
- docs/agents/* (issue-tracker, triage-labels, domain)
- every skills/<name>/SKILL.md and skills/catalog.json (descriptions must match what each
  skill/command now does)
- the CLAUDE.md command/architecture descriptions if they have gone stale
- the VitePress site under docs-site/ (its pages mirror the docs above — sync them too)
Treat this list as exhaustive: review each entry, don't generalize from the first few.

Spawn parallel subagents to do this — Opus does not fan out on its own. Dispatch one
subagent per doc cluster (e.g. CLI reference, architecture, studio/workflow, audio/assemble,
skills, docs-site) to audit its docs against the code concurrently, and keep working while
they run. Each subagent reports a drift list (doc location -> what's stale -> the correct
current behavior with the file/command that proves it).

Work in two passes:
1. AUDIT (parallel): produce a single consolidated drift inventory across all docs. Then
   show me that inventory and a short plan, and pause once for me there. If a doc is already
   accurate, say so and leave it untouched — don't churn correct prose.
2. UPDATE (after I approve): fix every confirmed drift. New/renamed/removed commands and
   flags, changed artifact shapes, new skills, the current command count, moved file paths,
   and dead references all get corrected. Add docs for genuinely undocumented commands or
   skills that now exist. Keep each doc's existing structure, voice, and depth — you're
   correcting facts, not rewriting style.

Conventions and guardrails:
- Match house style exactly: machine-readable examples, exact command syntax, kebab-case
  filenames, the .js import extensions when you reference source. Don't reformat a doc you
  aren't otherwise changing.
- Do NOT hand-edit the architecture diagram JPGs under docs/assets/ — those are generated
  from the Mermaid sources in docs/DIAGRAMS_SOURCE.md. If a diagram is stale, update the
  Mermaid block and note that the image needs regeneration; don't touch the JPG.
- The repo has doc guardrails: run `npm run check:cleanroom-docs` and
  `npm run check:skill-frontdoor` and keep them green; if you change skills/catalog.json keep
  its parity test passing; if the command count changed, update the assertion in
  cli-schema.test.ts. Run `npm run build` and `npm test` before declaring done.

Verify before you claim done. Before reporting a doc as fixed, confirm the corrected
statement against the actual code/--help output you read this session — quote the source.
If you couldn't verify something, flag it rather than guessing. Report faithfully: list
which docs you changed, which you confirmed already-correct, and anything you couldn't
verify.

When you finish, lead with the outcome — how many docs were stale, how many you corrected,
and that the guardrails and build pass — then the per-doc detail. Plain sentences, each doc
and command its own clause.
```