adr-helper

Creates Architecture Decision Records with unique numbers and prefilled metadata templates.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/cody-hutson/pmo-platform --skill adr-helper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr-helper
Source: https://github.com/cody-hutson/pmo-platform/tree/main/core/skills/adr-helper
Command: npx skills add https://github.com/cody-hutson/pmo-platform --skill adr-helper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The adr-helper Skill addresses the friction involved in writing and managing Architecture Decision Records (ADRs) within a platform environment, providing an efficient and organized approach to documenting key architectural decisions.

Core Features & Use Cases

  • Efficient ADR Scaffold: Automates the process of creating new ADRs, ensuring a standardized structure with pre-filled metadata and placeholders for prose.
  • Dynamic Home Resolution: Dynamically resolves the home directory for ADRs from predefined configurations, adapting to future changes.
  • Autonomous Allocation: Automatically assigns unique ADR numbers based on global counting across directories without the risk of collision or reuse.
  • Immutability Preservation: Upholds the principle of immutability for ADRs by avoiding editing, overwriting, or renumbering existing ADRs.

Quick Start

Run the 'adr-helper' Skill when prompted to "scaffold this as an ADR".

Frequently Asked Questions about adr-helper

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

FAQPage Schema
How do I automate Architecture Decision Record creation with standardized metadata?

Automating Architecture Decision Record creation involves allocating a unique global monotonic number for each record and pre-filling derived metadata into a template. This ensures standardization while leaving prose sections open for user input.

What is the best way to manage ADR numbering across multiple directories without collisions?

Managing ADR numbering across directories requires autonomous allocation of unique global monotonic numbers. This approach counts globally across all directories to assign identifiers without risking collisions or reusing previous numbers.

How do I scaffold a new Architecture Decision Record while preserving immutability of existing ones?

Scaffolding a new Architecture Decision Record while preserving immutability involves generating a new template with pre-filled metadata. The process strictly avoids editing, overwriting, or renumbering any existing records.

Can I integrate ADR scaffolding into a release pipeline workflow?

Architecture Decision Record scaffolding complies with standard schemas and templates, making it applicable within cross-cutting and release-pipeline-scoped contexts. It dynamically resolves the home directory for records from predefined configurations.

When do I need to use a standardized Architecture Decision Record template?

A standardized Architecture Decision Record template is needed when documenting key architectural decisions in a platform environment. It solves friction by providing an organized structure with pre-filled metadata and placeholders for prose.

Why does automated ADR generation leave prose sections empty?

Automated ADR generation leaves prose sections empty to separate structural metadata from human reasoning. It automates metadata pre-filling and unique number allocation, leaving the architectural context and decision prose for user input.