What problem does it solve? Keeping release documentation accurate and current is tedious: catalogs drift from the shipped surface, assessments lose their evidence, and documents go stale between releases. This Skill runs a release-documentation ceremony that constructs the entire documentation corpus from a current audit's records, so every claim traces back to a measurement taken at the release commit. ## Core Features & Use Cases - Audit-driven construction: Ensures a current audit exists (running /audit when the tree has moved past its stamp), then builds the catalog, assessments, and trap registry from the audit's extraction and determinations without measuring anything itself. - Vantage-split corpus: Produces a publishable layer in shipped vocabulary (catalog, assessments, traps) and an internal verification layer, keeping source paths and internal entry points out of publishable records. - Declared document types: Brings each document type declared under .ok-planner/surface/documents/ up to date at its target path, revising existing documents rather than rewriting them, and stamps everything with the release commit. - Use Case: After tagging a release, run /document v2.1.0 to regenerate the public catalog, story and assumption assessments, and trap registry from the audit, revise the README-style documents at their declared targets, and commit the stamped corpus in one commit. ## Quick Start Run /document with a release tag or commit to regenerate the project's documentation corpus from a current audit and commit the stamped records and documents.
