adr-writer

Name: adr-writer
Availability: InStock
Author: govctl-org

Generate and manage Architecture Decision Records with structured templates.

239|12|Updated Jan 17, 2026

Search Tags:#architecture #decision making #documentation #technical writing #adr #governance

Ready to run

npx skills add https://github.com/govctl-org/govctl --skill adr-writer-govctl-org

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: adr-writer
Source: https://github.com/govctl-org/govctl/tree/main/.claude/skills/adr-writer
Command: npx skills add https://github.com/govctl-org/govctl --skill adr-writer-govctl-org

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you create clear, consistent, and comprehensive Architecture Decision Records (ADRs) to document significant design decisions, ensuring better understanding and maintainability of your projects.

Core Features & Use Cases

ADR Creation: Generate new ADRs with a title.
Structured Content: Add context, decision rationale, consequences, alternatives, and references using specific commands.
Use Case: When a team needs to decide on a new database technology, they can use this Skill to create an ADR that outlines the problem, the chosen solution (e.g., PostgreSQL), the reasons for choosing it, the trade-offs (e.g., increased operational overhead), and alternatives considered (e.g., MySQL).

Quick Start

Use the adr-writer skill to create a new ADR with the title "Implement Feature Flags".

Frequently Asked Questions about adr-writer

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

FAQPage Schema

How do I document software architecture decisions for my team?▼

You can document software architecture decisions by generating Architecture Decision Records (ADRs) that provide structured templates for context, decisions, consequences, and alternatives. This enforces documentation discipline for design choices.

What should be included in an Architecture Decision Record?▼

An Architecture Decision Record should include the problem context, the chosen decision, rationale, trade-offs or consequences, alternatives considered, and references. This ensures traceability and clarity in software architecture.

How do I create a new ADR for a database technology selection?▼

To create a new ADR for database technology selection, use the creation command with a title. You can then add context, outline the chosen solution like PostgreSQL, state reasons, and document alternatives like MySQL.

What is the best way to enforce spec-first development for design choices?▼

The best way to enforce spec-first development is by managing ADRs through CLI commands for creating and updating records. This ensures documentation discipline and traceability for significant design decisions.

Can I update existing Architecture Decision Records as a project evolves?▼

Yes, you can update existing Architecture Decision Records by using specific CLI commands to add details, context, or references. This facilitates ongoing governance and maintains clarity as software architecture evolves.

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

You need to create an Architecture Decision Record when a team makes significant design decisions, such as adopting a new technology. It outlines the problem, chosen solution, reasons, trade-offs, and alternatives to ensure maintainability.