hads

Convert Markdown documentation into HADS format with SPEC, NOTE, and BUG blocks.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/ArogyaReddy/https-github.com-wshobson-agents --skill hads
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hads
Source: https://github.com/ArogyaReddy/https-github.com-wshobson-agents/tree/main/plugins/documentation-standards/skills/hads
Command: npx skills add https://github.com/ArogyaReddy/https-github.com-wshobson-agents --skill hads

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

HADS helps writers convert existing technical documentation into the Human-AI Document Standard, validate HADS documents, and optimize docs for token-efficient AI consumption.

Core Features & Use Cases

  • Convert Markdown documents into HADS-formatted content with SPEC, NOTE, and BUG blocks.
  • Validate HADS structure (frontmatter, manifest, and bolded blocks) to ensure compatibility with AI reading rules.
  • Optimize documentation readability and token efficiency for AI-assisted workflows.
  • Use Case: Convert a README to HADS format to enable reliable AI interpretation and automated quality checks.

Quick Start

Convert the provided documentation into HADS format to structure content into SPEC/NOTE/BUG blocks.

Frequently Asked Questions about hads

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert Markdown documentation for token-efficient AI reading?

HADS format is a structured documentation standard that optimizes text for token-efficient AI reading. It requires a frontmatter with name and description, an AI manifest, and properly formatted SPEC and BUG blocks to ensure reliable AI interpretation.

How do I validate HADS compliance for my technical documentation?

You validate HADS compliance by checking documents for required frontmatter, an AI manifest, and properly formatted bolded SPEC, NOTE, and BUG blocks. This ensures your documentation meets the standard for AI reading rules and automated quality checks.

What is token-efficient documentation formatting and when do I need it?

Token-efficient documentation formatting structures text into standardized blocks to reduce token consumption during AI processing. You need it when converting technical docs like READMEs to enable reliable AI interpretation and automated quality checks.

What's the best way to structure technical docs with SPEC and BUG blocks?

The best way to structure technical docs with SPEC and BUG blocks is converting existing Markdown into HADS format. This adds an AI manifest and frontmatter, creating a standardized structure that enables reliable AI interpretation and automated quality checks.

Does converting Markdown to HADS format require any dependencies?

Converting Markdown to HADS format requires no external dependencies. You can structure content into SPEC, NOTE, and BUG blocks and validate frontmatter directly without installing prerequisite packages or configuring environment setup.