skills.rest
rotnov
rotnovCOMMUNITY
Explore all skills by this author →
GitHub

create-architectural-decision-record

Create Architectural Decision Records using a repository-specific ADR template.

Updated Jul 24, 2026
Search Tags:#architecture#documentation#adr#engineering#decision-making
One-click install
npx skills add https://github.com/rotnov/pycc --skill create-architectural-decision-record-rotnov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-architectural-decision-record
Source: https://github.com/rotnov/pycc/tree/main/.agents/skills/create-architectural-decision-record
Command: npx skills add https://github.com/rotnov/pycc --skill create-architectural-decision-record-rotnov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the lack of historical context in software projects by providing a structured, consistent format for recording significant architectural decisions.

Core Features & Use Cases

  • Standardized Documentation: Ensures every Architectural Decision Record (ADR) follows a uniform template for clarity and maintainability.
  • Context Preservation: Captures the rationale, consequences, and trade-offs of technical decisions to prevent knowledge loss.
  • Use Case: When deciding between two database technologies for a new service, use this Skill to generate an ADR that documents the evaluation criteria and the final justification for the chosen path.

Quick Start

Use the create-architectural-decision-record skill to generate a new ADR document for the proposed migration to the new authentication service.

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 document architectural decisions and their trade-offs for my engineering team?▼

You document architectural decisions by creating an Architectural Decision Record (ADR) that standardizes technical design choices, capturing evaluation criteria, trade-offs, and justifications to prevent knowledge loss for engineering teams.

What is an Architectural Decision Record used for in software engineering?▼

An Architectural Decision Record is used to provide a structured, consistent format for recording significant technical design choices, ensuring long-term project maintainability by capturing historical context and trade-offs.

When do I need to create an ADR for a software project?▼

You need to create an ADR when making significant technical design choices, such as deciding between two database technologies or migrating authentication services, to document the evaluation criteria and final justification.

Do I need a specific template to generate an architectural decision record?▼

Yes, generating an architectural decision record requires adherence to the repository-specific ADR template defined in your project root directory to ensure uniform documentation and maintainability.

What is the best way to standardize technical design documentation across a repository?▼

The best way to standardize technical design documentation is to use an ADR template that enforces uniform formatting for every architectural decision, capturing context, consequences, and trade-offs for engineering teams.

Related Skills

Explore More Software Engineering Skills→
betaTridentbetaTrident

architecture-decision-records

Capture and maintain structured architectural decision records using a standard ADR template.

Community
Intermediate
AgentientAgentient
2

architectural-decision-records

Automate architectural decision documentation with standard ADR templates and lifecycle statuses.

Official
Intermediate
1479089714790897
7

kwp-engineering-architecture

Create and evaluate Architecture Decision Records documenting technical trade-offs.

Community
Intermediate
Ankurjain1121Ankurjain1121

architecture-decision-records

Create structured ADR documents with context, decision, and consequences sections.

Community
Basic