adr-writing

Creates and updates Architecture Decision Records using standardized templates and versioning/tracking workflows.

4|Updated May 1, 2026

Search Tags:#architecture #templates #documentation #adr #decision

Ready to run

npx skills add https://github.com/HigorAlves/orc --skill adr-writing-higoralves

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: adr-writing
Source: https://github.com/HigorAlves/orc/tree/main/orc/skills/adr-writing
Command: npx skills add https://github.com/HigorAlves/orc --skill adr-writing-higoralves

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the process of creating, updating, and managing Architecture Decision Records, ensuring consistent documentation of technical choices for easy future reference.

Core Features & Use Cases

Structured ADR Templates: Provides standardized templates to document decision context, options, and consequences.
Versioning & Tracking: Helps maintain history of decisions and their revisions over time.
Use Case: When a team needs to log a significant architectural choice like database selection or protocol standardization, this Skill facilitates writing and updating ADRs efficiently.

Quick Start

Use the adr-writing skill to create a new ADR with the next sequence number and populate it using the template.

Frequently Asked Questions about adr-writing

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

FAQPage Schema

What is an architecture decision record and when should I document one?▼

An architecture decision record (ADR) documents significant technical choices like database selection or protocol standardization. You should write an ADR whenever a team needs to log complex trade-offs, architectural evolutions, and decision context for future reference.

How do I write an architecture decision record using a structured template?▼

To write an architecture decision record, populate a standardized template documenting the decision context, considered options, and consequences. This ensures consistent documentation of technical choices and maintains standardized formats across the team for easy future reference.

How do I track versioning and revisions for historical architecture decisions?▼

You can track versioning for historical architecture decisions by updating the structured records over time. This process maintains a clear history of decision revisions and architectural evolutions, ensuring decision traceability and improving team knowledge retention.

What is the best way to document technical trade-offs for software architecture choices?▼

The best way to document technical trade-offs is by creating structured architecture decision records that capture the decision context, available options, and consequences. This approach supports technical leadership in tracing complex architectural evolutions efficiently.

Can I use this adr-writing skill for documenting protocol standardization and database selection choices?▼

Yes, you can use this skill to document protocol standardization and database selection choices. It facilitates creating and updating detailed architecture decision records with the next sequence number, ensuring these significant technical choices are logged efficiently.

Does this architecture decision documentation skill work without external dependencies?▼

Yes, this architecture decision documentation skill operates without external dependencies. It provides structured templates and reference components to facilitate creating and managing detailed records, ensuring adherence to standardized formats without requiring additional packages.