adr-writer

Capture and maintain Architecture Decision Records under docs/adr.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/Prathmesh2000/cursor_agent-orchestrator --skill adr-writer-prathmesh2000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adr-writer
Source: https://github.com/Prathmesh2000/cursor_agent-orchestrator/tree/main/agent-system/skills/adr-writer
Command: npx skills add https://github.com/Prathmesh2000/cursor_agent-orchestrator --skill adr-writer-prathmesh2000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ADRs help teams capture rationale for important technical decisions, preserving context and reducing re-litigations.

Core Features & Use Cases

  • Structured decision records: standardized templates that document context, options, decisions, and consequences.
  • Versioned history and searchability: ADRs stored under docs/adr and are easy to browse and reference.
  • On-demand governance and compliance: ensures decisions are revisited and tracked over time.

Quick Start

Create an ADR for a significant technical choice and store it under docs/adr with a standardized filename.

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 to stop teams from re-litigating technical choices?

You document architecture decisions by creating Architecture Decision Records that capture context, options, decisions, and consequences. This standardized documentation preserves rationale and reduces repeated debates across projects and teams.

What is the best way to structure and store ADRs for versioning and traceability?

The best way to structure ADRs is using a standardized template stored under docs/adr. This approach enables consistent versioning, searchability, and traceability across your technical decision history.

When do I need to create an Architecture Decision Record for my software project?

You need to create an Architecture Decision Record when making significant technical choices like selecting databases, libraries, or integration patterns. This ensures the evaluation of multiple options and their consequences are formally tracked.

How do I enforce standardized documentation for evaluating multiple architecture options?

You enforce standardized documentation by applying a consistent ADR template that requires detailing context, options, decisions, and consequences. This enforces on-demand governance and compliance for technical choices.

Can I use ADRs to manage governance and compliance for software architecture across multiple teams?

Yes, you can use ADRs to manage governance and compliance by ensuring technical decisions are revisited and tracked over time. Storing records under docs/adr provides a centralized, searchable history for cross-team traceability.

What are the limitations of relying on informal documentation instead of structured decision records?

Informal documentation lacks the standardized template needed to properly evaluate options, track consequences, and maintain versioning. Without structured decision records, you lose traceability and risk re-litigating settled technical choices.