Generate or update project documentation verified against the codebase
<cursor_skill_adapter>
gsd-docs-update or describes a task matching this skill.{{GSD_ARGS}}.{{GSD_ARGS}} as empty.When the workflow needs user input, prompt the user conversationally:
Use these Cursor tools when executing GSD workflows:
Shell for running commands (terminal operations)StrReplace for editing existing filesRead, Write, Glob, , , , , as neededGrepTaskWebSearchWebFetchTodoWriteWhen the workflow needs to spawn a subagent:
Task(subagent_type="generalPurpose", ...)model parameter maps to Cursor's model options (e.g., "fast")
</cursor_skill_adapter>Flag handling rule:
{{GSD_ARGS}}{{GSD_ARGS}}, 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)--force and --verify-only both appear in {{GSD_ARGS}}, --force takes precedence
</objective>
<execution_context> @C:/Users/gusta/OneDrive/Documentos/gerenciador-de-quadras/.cursor/get-shit-done/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 {{GSD_ARGS}}:
--force is active only if the literal --force token is present in {{GSD_ARGS}}--verify-only is active only if the literal --verify-only token is present in {{GSD_ARGS}}