h4tcher-domain-author

Create or modify governance audit domain files with scenario-based sub-agent checklists and invariant checks.

26|4|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/hatch3r/hatch3r --skill h4tcher-domain-author
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: h4tcher-domain-author
Source: https://github.com/hatch3r/hatch3r/tree/main/.claude/skills/h4tcher-domain-author
Command: npx skills add https://github.com/hatch3r/hatch3r --skill h4tcher-domain-author

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you create or update audit domain files in the hatch3r governance system with consistent structure, scenario-based checklists, and validated governance invariants.

Core Features & Use Cases

  • Domain standards alignment: Uses hatch3r governance documents to enforce required patterns for domain weighting, summary tables, and behavioral charters.
  • Reusable decomposition model: Guides you to study existing domains and produce a sub-agent decomposition with artifact counts and checklist coverage.
  • Governance invariant verification: Ensures summary-table rows exist, tier weight totals remain preserved, sub-agent totals match, and file length stays within the lean threshold.

Quick Start

Ask the assistant to create a new audit domain file under governance/audit/domains/ for your chosen tier and to update governance/AUDIT.md summary table and weight tables while verifying the invariants.

Frequently Asked Questions about h4tcher-domain-author

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

FAQPage Schema
How do I create governance audit domain files with sub-agent checklists?

Governance audit domain files are created by applying scenario-based sub-agent checklists and invariant-checked updates, requiring you to read governance/AUDIT.md and governance/CONSTITUTION.md to follow established domain file structure.

What is sub-agent decomposition for audit domains?

Sub-agent decomposition for audit domains is the process of splitting a governance domain into 4-6 sub-agents with artifact counts, checklist coverage, and boundary scope paragraphs to ensure comprehensive audit coverage.

How do I verify governance invariants when updating audit domain weights?

Verifying governance invariants involves checking summary-table rows, confirming tier weight totals remain preserved, matching sub-agent totals, and ensuring file length stays within the 30-80 line lean threshold.

Can I use this to assign Tier A-D domain placement for audit coverage?

Yes, you can use this to design Tier A-D domain placement by updating the Summary Table and Domain Weighting tables in governance/AUDIT.md while verifying weight subtotals and orphan-free domain coverage.

What are the lean thresholds and limitations for repository documentation in governance audits?

Repository documentation in governance audits is constrained by a 30-80 line lean threshold, requiring invariant verification to prevent orphan-free domain coverage gaps and mismatched sub-agent totals.

Do I need governance/AUDIT.md and governance/CONSTITUTION.md to write audit domains?

Yes, reading governance/AUDIT.md and governance/CONSTITUTION.md is required to enforce required patterns for domain weighting, summary tables, and behavioral charters before writing audit domain files.