create-architectural-decision-record

Generate standardized Architectural Decision Records from structured inputs.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/Ikki-Group/erp --skill create-architectural-decision-record-ikki-group
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-architectural-decision-record
Source: https://github.com/Ikki-Group/erp/tree/main/.agents/skills/create-architectural-decision-record
Command: npx skills add https://github.com/Ikki-Group/erp --skill create-architectural-decision-record-ikki-group

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ADRs are essential for documenting architectural decisions; this skill automates creating consistent Architectural Decision Records from structured inputs.

Core Features & Use Cases

  • Standardized ADR generation from inputs like Context, Decision, Alternatives, Stakeholders
  • Ensures front matter, sections, and rejection rationales follow the template
  • Produces machine-parseable and human-readable ADR documents stored under /docs/adr with proper naming

Quick Start

Provide DecisionTitle, Context, Decision, Alternatives, and Stakeholders to generate the ADR using the standard ADR template.

Frequently Asked Questions about create-architectural-decision-record

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

FAQPage Schema
How do I create an Architectural Decision Record from structured inputs?▼

To create an Architectural Decision Record, provide structured inputs like DecisionTitle, Context, Decision, Alternatives, and Stakeholders to automatically generate a standardized markdown document.

What is the standard format for saving architectural decision records in a project?▼

The standard format for saving architectural decision records is a markdown file named adr-NNNN-[title-slug].md, stored specifically within the /docs/adr/ directory structure.

How do I ensure my ADR documentation is machine-parseable for engineering teams?▼

To ensure ADR documentation is machine-parseable, generate outputs using a standardized template that codifies front matter and multi-item sections alongside human-readable markdown formatting.

Can I document architectural alternatives and rejection rationales automatically?▼

Yes, you can document architectural alternatives and rejection rationales automatically by supplying the Alternatives input, which the template processes into standardized ADR sections.

Do I need to manually format markdown front matter for software architecture decisions?▼

No, you do not need to manually format markdown front matter for software architecture decisions, as the generation process implements standardized front matter requirements automatically.