Docs update
Generate or update project documentation verified against the codebaseFrom its SKILL.md
npx -y skills add buildomator/buildomator --skill docs-updateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
2.2 KB, as published. Nobody here has run it
<objective>
Generate and update up to 9 documentation files for the current project. Each doc type is written by a gsd-doc-writer subagent that explores the codebase directly — no hallucinated paths, phantom endpoints, or stale signatures.
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 </objective>
<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/docs-update.md </execution_context>
<context> Arguments: $ARGUMENTSAvailable 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 </context>