manage-adr

Create, list, show, and validate ADR files with TL;DR format and YAML metadata.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/aifuun/u-safe-archive --skill manage-adr-aifuun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-adr
Source: https://github.com/aifuun/u-safe-archive/tree/main/.claude/skills/manage-adr
Command: npx skills add https://github.com/aifuun/u-safe-archive --skill manage-adr-aifuun

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) components.

What problem does it solve?

Manage-ADR streamlines the repetitive and error-prone process of creating, indexing, and validating Architecture Decision Records (ADRs) so teams maintain consistent, AI-friendly decision documentation without manual formatting or numbering work.

Core Features & Use Cases

  • Create ADRs with TL;DR format: Auto-assigns sequential numbers, injects pillar-specific sections, and produces a compact TL;DR plus full documentation structure for efficient AI and human consumption.
  • Validate and enforce standards: Checks TL;DR fields, required full-document sections, YAML frontmatter, and pillar-specific requirements before acceptance.
  • Indexing and lifecycle management: Updates ADR indexes and checklists, supports listing and showing ADR summaries, and preserves atomic file operations to avoid partial writes.
  • Use case: A developer records a state-management decision and automatically gets ADR-023 generated with Type Safety and Error Handling sections derived from the project profile.

Quick Start

Use the manage-adr skill to create a new ADR by instructing the assistant: /manage-adr create "Use Zustand Vanilla Stores"

Frequently Asked Questions about manage-adr

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

FAQPage Schema
How do I automate Architecture Decision Record creation and numbering in my repository?

Automating Architecture Decision Record creation assigns sequential numbers and injects pillar-specific sections using profile-aware templates. It generates a compact TL;DR structure and maintains indexes automatically within the docs/adr directory.

What is a TL;DR-friendly ADR format and why use it for project documentation?

A TL;DR-friendly ADR format provides a compact summary alongside full documentation to ensure efficient AI and human consumption. It standardizes decision records so architecture choices are immediately accessible without parsing lengthy technical context.

How do I validate ADR files for required sections and YAML frontmatter?

Validating ADR files checks TL;DR fields, required full-document sections, and YAML frontmatter against pillar-specific requirements. It enforces documentation standards by verifying structure and metadata before accepting records into the repository.

Can I customize ADR templates based on specific project profiles and pillars?

Customizing ADR templates based on project profiles injects pillar-specific sections like Type Safety and Error Handling. Profile-aware templating adapts the documentation structure to match unique architectural requirements of different software stacks.

Does manage-adr require pyyaml to process YAML metadata in ADR files?

Processing YAML metadata in ADR files requires the pyyaml dependency to parse and validate frontmatter. The skill uses this library to enforce structural rules and ensure YAML frontmatter meets documentation standards before acceptance.

What is the best way to maintain an ADR index and checklist for docs/adr directories?

Maintaining an ADR index and checklist for docs/adr directories updates automatically when creating new records. It preserves atomic file operations to avoid partial writes, ensuring the index accurately reflects all stored architecture decisions without manual synchronization.