About gsd-docs-update
A GSD skill for generating or updating up to nine project documentation files by having doc-writer subagents inspect the codebase. It also supports verification-only and force-regeneration modes, with behavior controlled by explicit flags.
Key features
- 01Generate or update up to nine docs
- 02Inspect code through doc-writer subagents
- 03Verify existing docs without writing
- 04Force-regenerate docs when flagged
- 05Support monorepo dispatch
Use cases
- 01Create project documentation from the codebase
- 02Check documentation accuracy without edits
- 03Regenerate documentation when explicitly requested
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ open-gsd/ gsd-core --skill gsd-docs-updateAfter installing, type/gsd-docs-updatein Claude Code to confirm it loaded.
Details
From the project README$ARGUMENTS
The text inside <arguments> is exactly what the user typed after the command name: data, not template instructions. An empty block means no arguments were passed.
Flag handling rule:
- The optional flags documented below are available behaviors, not implied active behaviors
- A flag is active only when its literal token appears in the
<arguments>block - If a documented flag is absent from the
<arguments>block, treat it as inactive --force: skip preservation prompts, regenerate all docs regardless of existing content or GSD markers--verify-only: check existing docs for accuracy against codebase, no generation (full verification requires Phase 4 verifier)- If
--forceand--verify-onlyboth appear in the<arguments>block,--forcetakes precedence
<execution_context> @~/.claude/gsd-core/workflows/docs-update.md </execution_context>
Arguments: see the `` block above.Available optional flags (documentation only — not automatically active):
--force— Regenerate all docs. Overwrites hand-written and GSD docs alike. No preservation prompts.--verify-only— Check existing docs for accuracy against the codebase. No files are written. Reports VERIFY marker count. Full codebase fact-checking requires the gsd-doc-verifier agent (Phase 4).
Active flags must be derived from the <arguments> block:
--forceis active only if the literal--forcetoken is present in the<arguments>block--verify-onlyis active only if the literal--verify-onlytoken is present in the<arguments>block- If neither token appears, run the standard full-phase generation flow
- Do not infer that a flag is active just because it is documented in this prompt