skills.rest
zinohome
zinohomeCOMMUNITY
Explore all skills by this author →
GitHub

adr-writer

Creates Architecture Decision Records documenting technical decisions with context, alternatives, and consequences.

Updated Mar 16, 2026
Search Tags:#design#documentation#markdown#adr#technical decisions#architecture decision record#tradeoffs
One-click install
npx skills add https://github.com/zinohome/RTMessage --skill adr-writer-zinohome
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adr-writer
Source: https://github.com/zinohome/RTMessage/tree/main/.github/skills/adr-writer
Command: npx skills add https://github.com/zinohome/RTMessage --skill adr-writer-zinohome

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often make important technical decisions without documenting the reasoning, alternatives, and tradeoffs, leading to repeated debates and lost institutional knowledge. This Skill produces structured Architecture Decision Records (ADRs) that capture the full decision context. ## Core Features & Use Cases - Structured ADR Template: Generates ADRs with context, decision, alternatives considered, tradeoffs, consequences, risks, and follow-up actions. - Status Workflow Guidance: Supports the ADR lifecycle from Proposed to Accepted, Deprecated, or Superseded, with numbering conventions. - Review Checklists: Includes best practices, anti-patterns, and review checklists to keep ADRs concise and accountable. - Use Case: When your team chooses PostgreSQL with TimescaleDB over ClickHouse and BigQuery for an analytics service, use this Skill to document the decision drivers, cost comparisons, risks, and assigned follow-up actions. ## Quick Start Ask the assistant to write an ADR for a specific technical decision, providing the context, the options considered, and the decision owner.

Frequently Asked Questions about adr-writer

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

FAQPage Schema
How do I write an Architecture Decision Record?▼

An ADR documents the context driving a decision, the decision itself, alternatives considered with pros and cons, tradeoffs, and consequences. Use the provided template covering status, date, deciders, risks, and follow-up actions with owners.

What should an ADR template include?▼

An ADR template should include status, date, deciders, context, the decision statement, 2-3 alternatives with pros and cons, tradeoffs, positive and negative consequences, risks with mitigations, and follow-up actions with deadlines.

When should I write an ADR versus skipping it?▼

Write ADRs for significant decisions like database selection, architecture patterns, or security approaches. Skip them for minor choices, since documenting every decision creates noise and 10-page ADRs that nobody reads are an anti-pattern.

How do ADR status transitions work?▼

ADRs move from Proposed to Accepted to Implemented, or get Rejected. Accepted ADRs can later become Deprecated and then Superseded by a newer ADR, creating a traceable decision trail across the project.

What are common ADR mistakes to avoid?▼

Common anti-patterns include overly long documents, missing alternatives that make decisions look predetermined, undocumented consequences, no assigned owner, and outdated statuses. Keep ADRs to 1-2 pages with honest tradeoffs.

Related Skills

Explore More Software Engineering Skills→
htxryanhtxryan
1

Researcher

Conducts deep research and produces structured survey documents for decision-making.

Community
Advanced
Anders-planckAnders-planck

docs-management

Standardize technical documentation creation, review, and publishing with templates and validation.

Community
Intermediate
dogeareddogeared

plan-eng-review

Define an end-to-end plan review workflow capturing architecture, data flow, edge cases, tests, and risk tradeoffs.

Community
Advanced
0xtaoist0xtaoist

ln-913-community-debater

Classify debate type and publish RFC or poll to GitHub Discussions via GraphQL.

Community
Advanced