Menu
Generate or update project documentation verified against the codebase
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Use this skill when the user wants direct operations on an Obsidian vault: read or edit notes and daily notes, search vault contents, count or list notes, manage tasks, move or rename files, find orphaned notes or broken links, inspect frontmatter/properties, manage sync or file history, query Bases, manage bookmarks, script the CLI, or run JavaScript against the Obsidian API. Trigger when the request implies "go into my vault and do X"; the user wants action on vault data, not an explanation. Skip pure conceptual or GUI-help questions such as settings navigation, theme/plugin installation, sync troubleshooting, Dataview syntax, keyboard shortcuts, or parsing vault files with unrelated external scripts.
Captures corrections, failures, missing capabilities, and reusable discoveries in agent so future work improves. Use this skill whenever a command, tool, or API fails unexpectedly; the user corrects the agent; the agent realizes its knowledge is outdated or wrong; a missing capability is exposed; or a better recurring approach is discovered. Record the result under .agents/learnings/, review related entries before major tasks, and promote durable workflow rules into AGENTS.md when they should change future behavior.
Generate tests for a completed phase based on UAT criteria and implementation
Generate an AI-SPEC.md design contract for phases that involve building AI systems.
Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit
Baseado na classificação ocupacional SOC
| name | gsd-docs-update |
| description | Generate or update project documentation verified against the codebase |
Flag handling rule:
$ARGUMENTS$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)--force and --verify-only both appear in $ARGUMENTS, --force takes precedence
<execution_context> @/home/aming/.config/opencode/gsd-core/workflows/docs-update.md </execution_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:
--force is active only if the literal --force token is present in $ARGUMENTS--verify-only is active only if the literal --verify-only token is present in $ARGUMENTS