write-adr

Generate Architecture Decision Records documenting context, options, and outcomes.

1|Updated Feb 13, 2026

Search Tags:#architecture #decision making #documentation #adr #technical decisions

Ready to run

npx skills add https://github.com/em-jones/staccato-toolkit --skill write-adr-em-jones

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-adr
Source: https://github.com/em-jones/staccato-toolkit/tree/main/.opencode/skills/write-adr
Command: npx skills add https://github.com/em-jones/staccato-toolkit --skill write-adr-em-jones

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams document their architectural decisions using the Architecture Decision Record (ADR) format, ensuring clarity and consistency in technical choices.

Core Features & Use Cases

ADR Generation: Creates new ADR documents based on a provided template.
Decision Tracking: Facilitates the recording of context, problem statements, considered options, and final decisions.
Use Case: When your team needs to decide on a new database technology, use this Skill to generate an ADR to formally document the evaluation process and the final choice.

Quick Start

Use the write-adr skill to create a new Architecture Decision Record.

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 one for my software project?▼

An Architecture Decision Record (ADR) documents significant technical decisions within a software project. You need an ADR to ensure clarity and consistency when making architectural choices, such as selecting a new database technology, by formally recording the evaluation process and final choice.

How do I document technical decisions and considered options for my architecture?▼

You can document technical decisions by generating an Architecture Decision Record that captures the context, problem statements, decision drivers, considered options, and final outcomes. This structured recording facilitates clear communication and historical tracking of architectural choices.

Can I use a standard template to track problem statements and decision drivers?▼

Yes, you can generate Architecture Decision Records based on a provided template. This template structures the recording of context, problem statements, considered options, and final decisions to facilitate clear communication and historical tracking of your architectural choices.

What is the best way to track architectural choices and context over time?▼

The best way to track architectural choices over time is by generating Architecture Decision Records. This approach facilitates the structured recording of context, problem statements, and outcomes, ensuring clear communication and historical tracking of technical decisions within a software project.

How do ADRs improve communication for technical decisions in software engineering?▼

Architecture Decision Records improve communication by facilitating the structured recording of context, problem statements, decision drivers, considered options, and outcomes. This ensures clarity and consistency in technical choices and provides a historical track of architectural decisions.