h4tcher-capability-add

Create hatch3r framework artifacts with gated validation and overlap checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It provides a lifecycle blueprint for adding new hatch3r framework artifacts while preventing duplicated overlap and enforcing repo-wide governance gates.

Core Features & Use Cases

  • Tiered addition workflow: Triages changes into T1/T2/T3 to determine whether to author inline or dispatch parallel sub-agents.
  • Overlap-block prevention: Scores cross-artifact overlap and blocks work when adding would exceed the >70% duplication threshold, routing to refactor instead.
  • Cross-skill delegation: Delegates body authoring to the correct author skill based on artifact type (content, adapter, or domain).
  • Stop-before-commit governance: Authors content, runs validation/test/typecheck/lint/build, regenerates inventory, and summarizes gates without committing.
  • Guardrails-first orchestration: Enforces “no branches, no commits, no PRs” and includes anti-slop and pillar compliance tests.

Quick Start

Ask an AI to execute the full Capability-Add lifecycle for your new artifact, then stop before commit after running the repo governance gates.

Frequently Asked Questions about h4tcher-capability-add

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

FAQPage Schema
How do I safely add new framework artifacts without creating duplicated overlap?

To safely add new framework artifacts, this skill triages change scope and enforces overlap constraints, blocking creation if cross-artifact duplication exceeds a 70% threshold. It routes blocked additions to a refactor workflow instead of authoring duplicates.

What is the tiered workflow for agentic coding when adding new modules?

The tiered workflow for agentic coding triages changes into T1, T2, and T3 levels to determine whether to author content inline or dispatch parallel sub-agents. This ensures correct delegation for tasks like adding agents, skills, rules, adapters, and hooks.

Does this module creation process run governance gates and tests automatically?

Yes, the module creation process automatically runs governance gates including validation, tests, typecheck, lint, and build steps. It also regenerates inventory and runs anti-slop and pillar compliance checks before stopping.

Can I use this skill to commit new adapters and rules directly to my repository?

No, you cannot use this skill to commit new adapters and rules directly. It operates with a strict stop-before-commit governance policy, meaning it authors content and runs checks but enforces a no-branches, no-commits, no-PRs guardrail.

When should I use inline authoring versus parallel task dispatch for content generation?

You should use inline authoring for T1 tier changes, while parallel task dispatch is used for T2 and T3 changes. The skill automatically triages the change scope to delegate body authoring to the correct content, adapter, or domain author skills.