Documentation Standards

Documentation Standards is a pair of agent skills from Seth Hobson's agents collection (wshobson/agents), a community project. They teach your agent two conventions for documents that agents and people both rely on. What its skills teach - hads: the Human-AI Document Standard, created by Nikša Barlović. It's plain Markdown where each block is tagged [SPEC] (terse facts), [NOTE] (human context), [BUG] (a verified failure with its symptom, cause and fix) or [?] (unverified), with a short reading instruction at the top that tells a model what to read and what to skip. Your agent can write new docs in HADS, convert an existing README, check that a document follows the rules, and answer from a HADS doc by reading its [SPEC] and [BUG] blocks first. - grounded-vault: a three-layer Markdown knowledge store: raw/ sources that are never edited, compiled wiki/ pages, and an archive/ for pages that drifted or were replaced. Every number, date or quote on a wiki page links to its source, each page records the git commit it was compiled against and the code paths it describes, and one git diff shows when a page has gone stale, without spending model tokens. How to install it In Claude Code, run /plugin marketplace add wshobson/agents, then /plugin install documentation-standards@claude-code-workflows. Codex CLI uses codex plugin marketplace add wshobson/agents, the repository has routes for Cursor, OpenCode, Antigravity CLI, GitHub Copilot and Pi, and npx skills add wshobson/agents installs single skills. Good to know - HADS needs no tooling: it's standard Markdown that any editor renders. The skill notes that a validator is planned but not included yet. - grounded-vault needs only a git repository. Its reference file covers a check script you can run from a pre-commit hook or CI, so a page can't land with an unsourced number or a stale fingerprint. - HADS is Nikša Barlović's open standard (MIT). The grounded-vault layout comes from the llm-wiki-loop project, which the skill treats as a reference rather than a dependency.

• “Write HADS documentation for this REST API.”

  Copy

• “Convert this README to HADS format.”

  Copy

• “Is this document valid HADS?”

  Copy

• “Summarize this HADS document from its SPEC and BUG blocks.”

  Copy

• “Set up a grounded vault for our architecture notes, with a source link on every claim.”

  Copy

• “Check which wiki pages have drifted from the code they describe.”

  Copy