skills.rest
rnavarych
rnavarychCOMMUNITY
Explore all skills by this author →
GitHub

role-architect:adr-writer

Write structured Architecture Decision Records with numbering and lifecycle status management.

14|3|Updated Feb 22, 2026
Search Tags:#architecture#documentation#system design#decision record#adr#technical debt
One-click install
npx skills add https://github.com/rnavarych/alpha-engineer --skill role-architect-adr-writer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: role-architect:adr-writer
Source: https://github.com/rnavarych/alpha-engineer/tree/main/plugins/roles/role-architect/skills/adr-writer
Command: npx skills add https://github.com/rnavarych/alpha-engineer --skill role-architect-adr-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of documenting significant architectural decisions, ensuring clarity, consistency, and a traceable history of design choices.

Core Features & Use Cases

  • ADR Creation: Guides the writing of Architecture Decision Records with a structured format.
  • Lifecycle Management: Manages the status transitions of ADRs (Proposed, Accepted, Deprecated, Superseded).
  • Linking Decisions: Facilitates linking related ADRs to show dependencies and evolution.
  • Use Case: When deciding on a new database technology, use this Skill to create a formal ADR, detailing the context, decision, consequences, and alternatives considered, ensuring team alignment and future reference.

Quick Start

Write a new Architecture Decision Record for using PostgreSQL for the Order Service.

Frequently Asked Questions about role-architect:adr-writer

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

FAQPage Schema
How do I write an Architecture Decision Record for a new system design?▼

Architecture Decision Records document significant design choices by detailing context, decision, consequences, and alternatives. This Skill guides structured ADR creation to ensure clarity, consistency, and traceable design history.

What is the best way to manage the lifecycle of an ADR?▼

Manage the ADR lifecycle by tracking status transitions from Proposed to Accepted, Deprecated, or Superseded. This approach maintains an accurate historical record as your system design and architectural choices evolve over time.

How do I link related Architecture Decision Records together?▼

Link related Architecture Decision Records to visualize dependencies and the evolution of decisions. This facilitates asynchronous team review processes by connecting related architectural choices and showing their impact across the system.

When do I need to document architecture decisions using ADRs?▼

You need to document architecture decisions using ADRs when making significant technical choices, such as selecting a new database technology. They provide formal documentation for team alignment, detailing context and consequences, and preventing accumulated technical debt.

Can I create lightweight ADRs for smaller technical decisions?▼

Yes, you can create lightweight ADRs for smaller technical decisions. This Skill supports lightweight formats while still managing ADR numbering and indexing to maintain a consistent and searchable log of architectural choices.

Related Skills

Explore More Software Engineering Skills→
jtvarisjtvaris

architecture-decision

Generate Architecture Decision Records with context, constraints, and alternatives.

Community
Intermediate
controlaltnerdcontrolaltnerd

adr

Create, review, and update Architecture Decision Records with status lifecycle management.

Community
Intermediate
nguyenpv1980-wqnguyenpv1980-wq
2

architecture-designer

Design software architecture from inspected codebase components and dependencies.

Community
Advanced
AgentientAgentient
2

architectural-decision-records

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

Official
Intermediate