Documentation

Keep docs in sync with code. Delegate the heavy lifting to the docs-manager agent, then capture decisions in a journal entry.

Overview

**Goal**: ./docs and architecture docs reflecting the latest code.
**Time**: 15–45 minutes.
**Tools used**: docs-manager agent, journal skill.

Prerequisites

A completed code change whose docs impact needs reflecting.
The ./docs folder initialized (or ready to be).

Step 1: Delegate the docs update

Ask the docs-manager agent to reconcile ./docs with the change — it updates the roadmap, changelog, architecture, and code-standards docs. The docs-manager is an agent (spawned by the orchestrator), not a slash command.

Delegate: "Update docs for the <feature> change in <files>"

Step 2: Capture a journal entry

Record the design decisions and gotchas as episodic memory for future sessions.

/vk:eng:journal

Next steps

New project — Docs seeding is part of bootstrapping.
Add a feature — The feature loop that triggers a docs update.