skills.rest
Sir-chawakorn
Sir-chawakornCOMMUNITY
Explore all skills by this author →
GitHub

write-adr

Capture technical decisions as structured Architecture Decision Records in Michael Nygard format.

9|3|Updated Jun 13, 2026
Search Tags:#architecture#documentation#adr#engineering#best-practices#decision-making
One-click install
npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill write-adr-sir-chawakorn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-adr
Source: https://github.com/Sir-chawakorn/sanook-cli/tree/main/skills/write-adr
Command: npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill write-adr-sir-chawakorn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of undocumented or poorly recorded technical decisions, which often lead to confusion, re-litigation of past choices, and architectural drift.

Core Features & Use Cases

  • Structured Documentation: Enforces the Michael Nygard ADR format to ensure context, alternatives, and consequences are captured.
  • Decision Lifecycle Management: Provides a clear workflow for proposing, accepting, and superseding decisions to maintain a clean, immutable history.
  • Use Case: When your team is debating between two database technologies, use this skill to formally record the chosen path, the rejected alternatives, and the long-term trade-offs for future reference.

Quick Start

Use the write-adr skill to document the decision to migrate our authentication service to Auth0 by outlining the context, alternatives, and consequences.

Frequently Asked Questions about write-adr

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

FAQPage Schema
How do I document architectural decisions to prevent architectural drift?▼

You document architectural decisions by capturing them as structured Architecture Decision Records. This skill enforces the Michael Nygard format to record context, alternatives, and consequences, ensuring consistent historical logging of system design evolution.

What is the best way to record technical trade-offs for future reference?▼

The best way to record technical trade-offs is using the ADR format. This skill formally captures the chosen path, rejected alternatives, and long-term consequences, preventing re-litigation of past choices and undocumented technical decisions.

How do I supersede a previous architectural decision in a repository?▼

You supersede previous architectural decisions through a structured lifecycle workflow. This skill provides a clear process for proposing, accepting, and superseding decisions to maintain a clean, immutable history within your project repository.

When do I need to write an Architecture Decision Record?▼

You need to write an Architecture Decision Record when your team is debating significant technical choices, such as migrating a service. It formally records the architectural choices and constraints to prevent future confusion.

Does this ADR format support append-only historical logging?▼

Yes, this ADR format supports append-only historical logging. It ensures consistent, immutable records of system design evolution by facilitating the documentation of architectural choices, trade-offs, and supersession logic.

Related Skills

Explore More Software Engineering Skills→
carson-sweetcarson-sweet
6

Manage Decisions

Record and track software architecture decisions in a project repository.

Community
Intermediate
chicanoandres702chicanoandres702

docs-architect

Extract architectural decisions and patterns from codebases into long-form technical documentation.

Community
Advanced
ThiagoVitaleThiagoVitale

gsd-complete-milestone

Archive completed milestones and update project documentation for the next version.

Community
Advanced
zoraxlzoraxl
3

wiki-query

Retrieves and synthesizes documentation, architecture decisions, and runbooks from a Markdown wiki repository.

Community
Intermediate