hex-adr-create

Create auto-numbered ADRs with dependency impact analysis and validation gates.

4|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/gaberger/hex --skill hex-adr-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hex-adr-create
Source: https://github.com/gaberger/hex/tree/main/.claude/skills/hex-adr-create
Command: npx skills add https://github.com/gaberger/hex --skill hex-adr-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ADR creation is manual, error-prone, and risks downstream breakage without a traceable dependency map and validation gates.

Core Features & Use Cases

  • Auto-numbered ADRs with timestamp-based ID and consumer dependency mapping.
  • Impact analysis across the workspace to identify affected artifacts and direct/transitive consumers.
  • Validate changes with explicit workplan gates to ensure builds, tests, and dependencies remain intact.
  • Use Case: When proposing a significant architectural change, generate an ADR that includes impact analysis and required validations before acceptance.

Quick Start

Provide the ADR title and brief context, and hex-adr-create will generate a numbered ADR with impact analysis and the necessary validation gates.

Frequently Asked Questions about hex-adr-create

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

FAQPage Schema
How do I automate Architecture Decision Record creation with dependency impact analysis?

Automate Architecture Decision Record creation by generating auto-numbered records with timestamp-based IDs that map consumer dependencies and identify affected artifacts across the workspace. Provide the ADR title and context to generate the document with full impact analysis and required validation gates.

What is the best way to prevent downstream breakage when restructuring code artifacts?

Preventing downstream breakage during code restructuring requires generating an Architecture Decision Record with cross-crate checks and explicit validation gates. This maps direct and transitive consumers to ensure builds, tests, and dependencies remain intact before the proposed change is accepted.

How do I generate an ADR with cross-crate checks and validation gates?

Generate an ADR with cross-crate checks by providing a brief context for the architectural change. The automated process creates a numbered ADR that maps consumer dependencies and embeds explicit workplan validation gates to verify that builds and tests pass.

When do I need an Architecture Decision Record with consumer dependency mapping?

An Architecture Decision Record with consumer dependency mapping is needed when proposing changes that modify, delete, or restructure code artifacts across the workspace. It traces direct and transitive consumers to validate that builds and dependencies remain intact.

Can I use automated ADR generation for changes that delete or modify workspace artifacts?

Automated ADR generation applies directly to changes that modify, delete, or restructure code artifacts across the workspace. It maps the consumer dependencies and applies validation gates to ensure tests and builds remain intact before the restructuring is accepted.

Why does manual ADR creation risk downstream breakage in a workspace?

Manual ADR creation risks downstream breakage because it lacks a traceable consumer dependency map and explicit validation gates. Automating the process maps direct and transitive consumers across crates to identify affected artifacts before workplan acceptance.