doc-review

# `/gflow:doc-review` — Documentation Review Gate Run this gate before cutting a release. Two phases: 1. **Mechanical checks** (sections 1–7 below) — fast, scripted, deterministic. Run inline. 2. **LLM council audit** (section 8) — 3 parallel review subagents, then consensus synthesis. The mechanical pass catches stale strings and dead links; the council catches drift between docs, fictional claims, and gaps a human reader would notice. Every item reports **PASS / UPDATED / WARN / FAIL**. Any **FAIL** or any **RED** council verdict blocks the release. > **Provenance:** the council protocol below was validated on the v0.8.1 docs refresh release (2026-05-23). The audit found 11 fixable issues that the mechanical checklist alone missed (e.g., the `experimental/` subpackage fiction in 3 files, the `gflow video i2v` non-working hero snippet in README). Keep the council step — it pays for itself. --- ## 0 · Pre-flight - Confirm you are on the release branch (`release/vX.Y.Z` or `hotfix/...`), not on `develop` or `main`. - If a release spec exists at `docs/superpowers/specs/YYYY-MM-DD-*-design.md`, identify it now — the council auditors will use it as the ground truth for "what was supposed to ship." - If there is no spec, that is also fine — the council will work from the docs alone, but flag the absence as a process risk. --- ## 1 · Version references Check these files for stale version strings (old numbers, outdated status labels): | File | What to verify | |---|---| |...