gsd-docs-update

To generate and verify project documentation, this Skill automates documentation creation directly against the codebase. It uses the gsd-doc-writer workflow to produce up to nine aligned docs while enforcing a frontmatter-driven workflow for accuracy.

To verify existing project docs without applying changes, you can use the --verify-only flag. This validates that your current documentation matches the codebase and gracefully flags any drift without regenerating the files.

The best way to regenerate outdated documentation across multiple modules is by using the --force flag. This overrides preservation prompts and triggers the gsd-doc-writer to rebuild up to nine project docs from the latest code structure.

Yes, you can integrate documentation generation into an automated software engineering workflow for onboarding and compliance. The Skill supports an end-to-end workflow from code discovery to publication, keeping living documentation continuously in sync.

Documentation drifts from the codebase during maintenance when updates are manual, but you prevent it by running automated verification directly against the source code. This ensures ongoing accuracy, consistency, and alignment for compliance.

Yes, the documentation update workflow explicitly supports software projects with multiple modules. It enforces a frontmatter-driven workflow, respects preservation prompts, and integrates with a gsd-doc-writer subagent to manage the doc set.