gsd-docs-update

Project documentation matching your live codebase is generated by spawning subagent writers that explore the repository and produce docs without inventing paths or signatures. This ensures your documentation accurately reflects your actual source files.

Yes, you can verify existing documentation without overwriting by running the update process with the literal --verify-only flag. This checks your current docs against the codebase and reports results without writing any changes to files.

Updating stale docs across a monorepo is handled through multi-file dispatch and selective regeneration. The workflow reads the repository with file-level inspection and preserves workflow gates while regenerating documentation across multiple project packages.

Codebase documentation generation supports per-file preservation and honors workflow gates during the update process. It reads the repository, runs subagent writers, and writes or reports results while maintaining your existing repository validation rules.

To force overwrite outdated documentation files, use the literal --force flag when running the documentation update. This bypasses preservation and overwrites existing docs with newly generated, code-verified content.

Manually edited documentation becomes stale because it relies on human updates rather than codebase verification. Automated doc generation eliminates this by reading live source files and verifying signatures and paths to ensure ongoing accuracy.