gsd-docs-update

To automatically generate and verify project documentation against your codebase, trigger the docs-update workflow to regenerate docs and detect drift. The workflow uses subagents to explore the codebase, ensuring consistency across APIs, modules, and design notes.

Documentation drift occurs when project docs become outdated relative to the current codebase. You prevent it by applying automated verification and drift detection workflows that check documentation correctness against APIs and design notes, ensuring docs stay aligned.

You can check existing documentation for correctness without regenerating everything by using the verify-only mode. This flag-driven behavior enforces documentation correctness by detecting drift against the current codebase while optionally preserving existing docs.

Automated documentation generation works for repositories with multiple doc types and languages. The workflow applies dedicated subagents to explore the codebase, ensuring consistency across diverse APIs, modules, and design notes throughout the project.

The best way to force documentation regeneration for a project is by using the force regeneration flag. This flag-driven control overrides default behaviors, triggering dedicated subagents to automatically generate fresh docs and verify them against the current codebase.