hads

To convert Markdown documentation for AI readability, feed the document to the HADS skill to automatically generate HADS-formatted content with required frontmatter, [SPEC]/[NOTE]/[BUG] blocks, and an AI manifest for model reasoning.

HADS formatting standardizes technical writing by structuring Markdown with frontmatter, specific block types, and an AI manifest. It is needed to provide consistent ground-truth facts and context so AI models can accurately read and reason about documentation.

You validate Markdown frontmatter and block types for AI-readability by checking that documents include required HADS elements like an H1 title, version, a manifest, and properly structured [SPEC]/[NOTE]/[BUG] blocks to guide model behavior.

Yes, you can migrate technical documentation to HADS without losing human readability. The conversion process applies documentation migration workflows that optimize token efficiency and maintain consistent structure for both humans and AI.

Documentation migration to HADS format does not require external dependencies. The skill processes existing Markdown documents independently, applying validation guidance and structural conversion without needing additional components or libraries.

You should not use HADS formatting for documentation that does not require AI reasoning or ground-truth context. It is specifically designed for technical writing, documentation migration, and knowledge transfer scenarios where AI models need structured facts.