adr-creator

Create Architecture Decision Records as Markdown files under docs/adr.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/zazu-22/ff_data_analytics --skill adr-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr-creator
Source: https://github.com/zazu-22/ff_data_analytics/tree/main/.claude/_archive_skills/adr-creator
Command: npx skills add https://github.com/zazu-22/ff_data_analytics --skill adr-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps teams Create Architecture Decision Records (ADRs) documenting significant technical decisions for the FF Analytics platform. It guides the ADR process from context gathering to documentation, ensuring decisions are traceable, well-rationalized, and easy to reference in the future.

Core Features & Use Cases

  • End-to-end ADR workflow from context to final documentation
  • Standard ADR templates and structure to ensure consistency
  • Automated ADR numbering via the provided script
  • When to use: for data model choices, infrastructure decisions, or conformance topics; useful when evaluating alternatives or updating prior ADRs

Quick Start

Run the ADR creation workflow by first determining the next ADR number with the provided script and then generating an ADR draft:

  • Execute scripts/get_next_adr_number.py to retrieve the next ADR number (e.g., ADR-015)
  • Run scripts/create_adr.py to create a new ADR draft and populate docs/adr/ADR-015-<slug>.md, then edit the sections as needed

Frequently Asked Questions about adr-creator

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

FAQPage Schema
How do I create architecture decision records for my project?

Architecture Decision Records (ADRs) document significant technical decisions with context, alternatives, and trade-offs. This Skill automates ADR creation by guiding you through the workflow, applying a standard template, auto-generating ADR numbers, and producing versioned Markdown files in docs/adr for traceability and future reference.

When should I use ADRs to document technical decisions?

Use ADRs when evaluating architectural choices—data models, infrastructure options, conformance policies, or identity systems. They're essential when comparing alternatives ("should we use X or Y"), updating prior decisions, or establishing a traceable record of why technical direction was chosen.

How do I get started creating an ADR with automated numbering?

Execute scripts/get_next_adr_number.py to retrieve the next ADR number, then run scripts/create_adr.py to generate a draft ADR file. The Skill populates the template structure and Markdown output; you then edit the context, alternatives, decision, and consequences sections.

Can I use ADRs across different types of technical decisions?

Yes. ADRs apply to data model choices, infrastructure decisions, data quality policies, and identity or conformance topics. The standard template and workflow accommodate any significant architectural decision where alternatives and trade-offs need documentation.

What happens when I need to update or supersede an existing ADR?

The Skill supports versioning and ADR updates through the automated numbering and template structure. When modifying prior decisions, you can create new numbered ADRs that reference and supersede earlier ones, maintaining a complete decision history.