update-docs

To keep project documentation in sync with code changes, an automated doc-keeper workflow gathers context from git and current docs to reconcile updates across CLAUDE.md, tasks.md, specs, design.md, changelog, and glossary after feature additions or bug fixes.

An AI-assisted doc-keeper updates a changelog and glossary by spawning an agent that gathers context from recent git history and current documentation, applying updates automatically to reconcile architectural changes and feature completions.

Yes, you can initialize project documentation from an existing codebase using Bootstrap mode, which creates initial docs including CLAUDE.md, tasks.md, specs, design.md, changelog, and glossary.

The best way to update design.md and specs after architectural changes is using Update mode, which spawns a doc-keeper agent to reconcile only changed files by gathering context from git history.

Yes, git is needed to automate documentation maintenance because the doc-keeper agent relies on gathering context from git history to identify recent codebase changes and apply corresponding documentation updates.

You should not use automated docs-maintenance when no code changes have occurred, as Update mode specifically targets changed files by gathering context from git history to reconcile only modified documentation.