write-adr

Create, revise, and manage Architectural Decision Records for software architecture.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/Dektora/dekspec-public --skill write-adr-dektora
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-adr
Source: https://github.com/Dektora/dekspec-public/tree/main/plugins/dekspec/skills/write-adr
Command: npx skills add https://github.com/Dektora/dekspec-public --skill write-adr-dektora

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation, management, and review of Architectural Decision Records (ADRs), streamlining the process of documenting and tracking architectural decisions within a team.

Core Features & Use Cases

  • Automated ADR Creation: Generate ADRs from descriptions, ensuring consistency and completeness.
  • Audit and Review: Perform quality checks and interactive reviews of ADRs.
  • Revision and Supersession: Revise existing ADRs and create new ones that supersede old ones.
  • Locking and Unlocking: Lock ADRs to prevent further changes and unlock for updates.
  • Use Case: When a team needs to document an architectural decision, use this Skill to create an ADR that captures the decision, its rationale, and its consequences.

Quick Start

Use the /write-adr command to create a new ADR with the description 'Implement a new API endpoint for user authentication.'

Frequently Asked Questions about write-adr

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

FAQPage Schema
How do I create an Architectural Decision Record for a new software architecture?

To create an Architectural Decision Record, provide a description of your architectural decision and the system generates a complete ADR capturing the rationale and consequences. It validates the decision against existing architecture elements to ensure consistency.

What is the process for revising and superseding existing Architectural Decision Records?

Revising Architectural Decision Records involves unlocking the original ADR, applying changes, and optionally creating a new ADR that supersedes the old one. The system tracks supersession relationships to maintain a clear audit trail of architectural changes over time.

Can I lock an Architectural Decision Record to prevent further modifications?

Yes, you can lock an Architectural Decision Record to prevent unauthorized changes to accepted architectural decisions. Locking secures the ADR status, and you must explicitly unlock it before applying any revisions or updates.

How does automated ADR review and audit work for software architecture decisions?

Automated ADR review performs quality checks on your architectural decision records by validating the reasoning against existing architecture elements. The system conducts interactive reviews to ensure completeness, consistency, and precise architectural reasoning before acceptance.

Do I need existing architecture documentation before generating an ADR?

Existing architecture documentation is not strictly required but is highly beneficial for validation. The system validates new Architectural Decision Records against existing architecture elements and decisions to ensure precise reasoning and structural consistency within your software architecture.

What are the limitations of automating Architectural Decision Record management?

Automating Architectural Decision Record management requires precise architectural reasoning to function correctly. The system cannot generate valid ADRs from vague descriptions and relies on accurate validation against existing architecture elements to maintain decision quality during creation and supersession.