skills.rest
thinceller
thincellerCOMMUNITY
Explore all skills by this author →
Website𝕏@thinceller_devGitHub

write-adr

Creates ARC/ADR-style decision records documenting rationale, alternatives, statuses, and tradeoffs for technical choices in software projects.

4|Updated Aug 1, 2020
Search Tags:#architecture#documentation#decision record#adr#technical design#project governance
One-click install
npx skills add https://github.com/thinceller/thinceller.net --skill write-adr-thinceller
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-adr
Source: https://github.com/thinceller/thinceller.net/tree/main/.claude/skills/write-adr
Command: npx skills add https://github.com/thinceller/thinceller.net --skill write-adr-thinceller

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you record important architecture and technical decisions in a consistent ADR format so future changes are easier to understand, review, and maintain.

Core Features & Use Cases

  • ADR Creation: Draft a new Architecture Decision Record in docs/adr/ with the required structure.
  • Decision Guidance: Helps identify when a change is significant enough to document, such as introducing a new library, changing rendering strategy, or altering a data model.
  • Lifecycle Management: Supports ADR statuses like proposed, accepted, rejected, deprecated, and superseded, including references when one decision replaces another.
  • Use Case: After adopting a new framework or changing a build pipeline, you can capture the rationale, alternatives, and tradeoffs in a reusable project record.

Quick Start

Ask the assistant to create an ADR for a recent technical decision and include what was decided, why it was chosen, and which alternatives were considered.

Frequently Asked Questions about write-adr

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

FAQPage Schema
What is an architecture decision record and when do I need to create one?▼

An architecture decision record (ADR) documents significant technical choices like introducing libraries, changing rendering strategies, or altering data models to ensure future changes are easier to understand and maintain.

How do I document technical design tradeoffs and alternatives for a new framework adoption?▼

You can draft an architecture decision record in a consistent format to capture the decision, rationale, alternatives, and tradeoffs for your new framework adoption, recording it directly in your project documentation.

Can I track the lifecycle status of architecture decisions from proposed to deprecated?▼

Yes, you can manage architecture decision record statuses including proposed, accepted, rejected, deprecated, and superseded, and add references when a new decision replaces a previous one.

What is the best way to maintain project governance documentation when changing implementation strategies?▼

Recording implementation strategy changes in a standardized architecture decision format within your project documentation ensures the rationale and tradeoffs are consistently captured for review and maintenance.

When should I not use an architecture decision record for project updates?▼

You should avoid creating an architecture decision record for minor updates that do not represent significant technical choices, reserving the format for decisions like altering data models or introducing new build pipeline workflows.

Related Skills

Explore More Software Engineering Skills→
majesticlabs-devmajesticlabs-dev
47

create-adr

Create standardized Architecture Decision Records with a versioned naming convention.

Official
Advanced
tkstangtkstang

oat-pjm-update-repo-reference

Update OAT repository reference documentation, backlog, roadmap, and decision records.

Community
Advanced
1479089714790897
7

kwp-engineering-architecture

Create and evaluate Architecture Decision Records documenting technical trade-offs.

Community
Intermediate
boomNDSboomNDS

architecture

Capture architectural decisions with ADR templates and rationale.

Community
Basic