skills.rest
vecear
vecearCOMMUNITY
Explore all skills by this author →
GitHub

adr-writer

Creates Architecture Decision Records with context, alternatives consequences and owners.

Updated Jan 21, 2026
Search Tags:#architecture#templates#documentation#adr#governance#engineering#decision-record
One-click install
npx skills add https://github.com/vecear/Nipponverb --skill adr-writer-vecear
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adr-writer
Source: https://github.com/vecear/Nipponverb/tree/main/.claude/skills/adr-writer
Command: npx skills add https://github.com/vecear/Nipponverb --skill adr-writer-vecear

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture Decision Records (ADRs) provide a structured, auditable way to capture reasoning behind major tech choices, including context, alternatives, and consequences.

Core Features & Use Cases

  • Templates and guided structure for consistent ADRs across projects.
  • Tracks context, decision, alternatives, consequences, and owners to ensure accountability.
  • Useful for decisions like database selection, authentication strategy, deployment patterns, and governance.

Quick Start

Create a new ADR document titled 'ADR-001: [Title]' with sections for Context, Decision, Alternatives, Consequences, and Owners.

Frequently Asked Questions about adr-writer

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

FAQPage Schema
How do I document architecture decisions for database selection and deployment patterns?▼

To document architecture decisions, use a structured template capturing context, alternatives, consequences, and owners. This ensures traceability and accountability for major technical choices across teams.

What is an Architecture Decision Record and when do I need one?▼

An Architecture Decision Record (ADR) is a structured document capturing the reasoning behind major technical choices. You need an ADR when making significant decisions like selecting a database or defining an authentication strategy.

How to write an Architecture Decision Record that ensures traceability and accountability?▼

Write an Architecture Decision Record by defining a clear template with sections for context, decision, alternatives, consequences, and explicit owners, enforcing a structured workflow with revision history for auditability.

Can I use a standard ADR template for governance and engineering decisions across different teams?▼

Yes, you can enforce a consistent ADR template across teams for governance and engineering decisions. It provides guided structure and tracks revision history to ensure consistency and auditability for various technical decisions.

What is the best way to track context and alternatives in technical decision records?▼

The best way to track context and alternatives is using a structured decision record workflow that explicitly documents these sections alongside consequences and owners, ensuring all reasoning is auditable.

Why does my team need a structured workflow for architecture documentation?▼

Your team needs a structured workflow for architecture documentation to prevent knowledge loss and ensure accountability. It captures revision history and explicit owners, making the reasoning behind major technical decisions auditable.

Related Skills

Explore More Software Engineering Skills→
abdullah1854abdullah1854
1

session-handoff

Generate Markdown Architectural Decision Records from structured inputs.

Community
Intermediate
joshbandjoshband
3

docs

Validate YAML frontmatter metadata and generate auditable change history for LocusQ documentation.

Community
Intermediate
DomainLangDomainLang
16

software-architect

Create and inspect ADRs and PRSs with DDD alignment.

Official
Advanced
jrodrigopucajrodrigopuca

context-compactor

Save conversational decisions, steps, and context into organized markdown files.

Community
Intermediate