ADR Authoring Skill

Automate creation, validation, and lifecycle management of Architecture Decision Records.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/Ankh-Studio/copilot-enterprise-eval-plugin --skill adr-authoring-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ADR Authoring Skill
Source: https://github.com/Ankh-Studio/copilot-enterprise-eval-plugin/tree/main/skills/adr-authoring
Command: npx skills add https://github.com/Ankh-Studio/copilot-enterprise-eval-plugin --skill adr-authoring-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires fs, path, crypto, and includes scripts (resource) and assets (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the creation and management of Architecture Decision Records (ADRs), ensuring that critical architectural choices are well-documented, evidence-based, and maintainable.

Core Features & Use Cases

  • Automated Evidence Gathering: Scans repositories to find relevant code, issues, and documentation to support ADRs.
  • Quality Validation: Enforces ADR quality standards through automated checks and scoring.
  • Lifecycle Management: Tracks ADRs from proposal to deprecation, managing relationships between decisions.
  • Use Case: When deciding on a new state management library, this Skill can analyze existing patterns, suggest options with pros/cons, and help draft an ADR that links directly to relevant code snippets and existing issues.

Quick Start

Use the adr-authoring skill to create a new ADR about choosing a state management library.

Frequently Asked Questions about ADR Authoring Skill

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

FAQPage Schema
How do I create Architecture Decision Records with evidence from my repository?

Architecture Decision Records are created by scanning your repository to gather relevant code, issues, and documentation, automatically linking this evidence to support architectural decisions. The skill enforces quality standards and manages the ADR lifecycle from proposal to deprecation.

When do I need to document architectural decisions in a software repository?

Documenting architectural decisions is needed when selecting new libraries, altering state management, or changing structural patterns. It ensures critical choices are maintainable and evidence-based, tracking relationships between decisions from initial proposal through deprecation.

How does automated validation enforce ADR quality standards?

Automated validation enforces ADR quality standards by running scripts that check and score architectural decision records against predefined criteria. This ensures documentation consistency and structural integrity before decisions are formally accepted into the repository.

Can I use repository analysis to find existing architectural patterns for decision records?

Repository analysis identifies existing architectural patterns by scanning code and documentation to find relevant snippets and issues. This automated evidence gathering provides the necessary context and pros and cons to draft informed decision records.

What is the best way to manage the lifecycle of architectural decision records?

Managing the lifecycle of architectural decision records is best handled by tracking each decision from proposal to deprecation while maintaining relationships between linked records. This ensures structural context is preserved as the software architecture evolves.

Does this ADR authoring skill integrate with other repository assessment tools?

The ADR authoring skill supports integration with other repository assessment and recommendation skills. This allows architectural decisions to be evaluated alongside broader code quality and structural analysis workflows within the same environment.