/docs update#

Refresh project-level documentation after meaningful code or architecture changes.

Usage#

/docs update

Good Times To Run It#

• after shipping a major feature
• after architecture or deployment changes
• before a formal handoff
• when project docs have clearly drifted

How It Relates To Task-Level Docs Sync#

CafeKit already performs lightweight task closeout docs checkpoints after verified task completion.

Use /docs update for broader project docs, not for every small implementation change.