hads

Version 1.0.0 · Human-AI Document Standard · 2026 · HADS 1.0.0 This skill teaches Claude how to read, generate, and validate HADS documents. Read all [SPEC] blocks before responding to any HADS-related request. Read [NOTE] blocks if you need context on intent or edge cases. [SPEC] [SPEC] Block tag rules: [SPEC] Required elements in order: [SPEC] When encountering a HADS document: Token optimization: for large documents, scan section headings first, then read only [SPEC] and [BUG] blocks in relevant sections. [SPEC] When asked to write documentation in HADS format: Content rules for [SPEC] : Content rules for [BUG] : [NOTE] When converting existing documentation to HADS: extract facts into [SPEC] , move narrative and history to [NOTE] , surface all known issues as [BUG] . Do not duplicate content between block types. [SPEC] A valid HADS document must have: Validator: (planned — not yet included in this release) [SPEC] User: "Write HADS documentation for this REST API" → Generate full HADS document: header, manifest, sections with [SPEC]/[NOTE]/[BUG] blocks User: "Convert this README to HADS format" → Restructure existing content into HADS blocks, preserve all facts, add manifest User: "Is this document valid HADS?" → Check: H1 title, version, manifest, block tag formatting, BUG block completeness User: "Summarize this HADS document" → Read only [SPEC] and [BUG] blocks, return...