Gsd:docs Update
Documentsgsd:docs-updateGsd:docs Update is an Agent Skill for documents published in the davepoon/buildwithclaude repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Generate or update project documentation verified against the codebase
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/davepoon/buildwithclaude/blob/HEAD/plugins/gsd/skills/docs-update/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/gsd-docs-update, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
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
$ARGUMENTS - If a documented flag is absent from
$ARGUMENTS, 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$ARGUMENTS,--forcetakes precedence
<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/docs-update.md </execution_context>
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 $ARGUMENTS:
--forceis active only if the literal--forcetoken is present in$ARGUMENTS--verify-onlyis active only if the literal--verify-onlytoken is present in$ARGUMENTS- 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