adr-writer
ADR Writer guides you through building comprehensive Architecture Decision Records that capture the reasoning behind key technical choices. It provides a structured template covering context, decision rationale, alternatives evaluated, tradeoffs made, and consequences—helping teams document and communicate architecture decisions clearly.
ADR Writer helps you create structured Architecture Decision Records that document technical choices with context, alternatives, and consequences.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-01-12
ADR Writer helps you create structured Architecture Decision Records that document technical choices with context, alternatives, and consequences. ADR Writer guides you through building comprehensive Architecture Decision Records that capture the reasoning behind key technical choices. It provides a structured template covering context, decision rationale, alternatives evaluated, tradeoffs made, and consequences—helping teams document and communicate architecture decisions clearly.
Use it when
- ADR Writer's template covers all essential sections: context (the issue requiring a decision), decision (what was chosen).
- ADR Writer structures your documentation to explicitly list and evaluate alternative approaches alongside your chosen solution.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Install
patricio0312rev/skills/adr-writer
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How to write architecture decision records with ADR Writer?
ADR Writer guides you through building comprehensive Architecture Decision Records that capture the reasoning behind key technical choices. The tool provides a structured template covering context, decision rationale, alternatives evaluated, tradeoffs made, and consequences—helping teams document and communicate architecture decisions clearly.
What does an ADR Writer template include?
ADR Writer's template covers all essential sections: context (the issue requiring a decision), decision (what was chosen), alternatives (other options considered), tradeoffs (benefits and drawbacks), and consequences (impacts of the choice). This comprehensive structure ensures technical decisions are fully documented for team review and future reference.
How can ADR Writer help document architecture decisions with alternatives?
ADR Writer structures your documentation to explicitly list and evaluate alternative approaches alongside your chosen solution. By capturing what was considered and why alternatives were rejected, ADR Writer creates a complete decision record that shows the full reasoning process and helps teams understand the context behind technical choices.
Can ADR Writer establish a decision log for engineering teams?
Yes. ADR Writer helps build a decision log to maintain accountability and visibility of technical decisions across your team. By generating consistent, structured Architecture Decision Records, the tool enables teams to track consequences and risks of architectural choices over time and maintain a searchable history of decisions.
What are architecture decision record best practices with ADR Writer?
ADR Writer implements best practices by providing a standardized format that captures decision context, rationale, and tradeoffs in one place. This approach ensures decisions are documented while fresh, communicated clearly to stakeholders, and preserved for future team members who need to understand why specific technologies or design patterns were selected.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
ADR Writer
Document architecture decisions with clear context, alternatives, and consequences.
ADR Template
```markdown
ADR-001: [Title of Decision]
Status: Proposed | Accepted | Deprecated | Superseded by ADR-XXX Date: 2024-01-15 Deciders: Alice (Tech Lead), Bob (Principal Engineer) Owner: Alice
Context
What is the issue we're facing? What factors are driving this decision?
We need to choose a database for our new analytics service. Current requirements:
- 10M+ events per day
- Complex aggregation queries
- Real-time dashboards
- Budget: $5k/month
- Team familiar with SQL
Decision
We will use PostgreSQL with TimescaleDB extension.
Alternatives Considered
Option 1: PostgreSQL + TimescaleDB (CHOSEN)
Pros:
- Team already knows PostgreSQL
- Time-series optimization for analytics
- Reliable and proven
- Good query performance
- Reasonable
(truncated - see the full file via the links below)
File tree — 1 file
architecture/adr-writer/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Create a structured ADR to document a technical decision with alternatives and tradeoffs”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
ADR Writer helps teams document architectural decisions in a structured, numbered format that captures context, alternatives considered, and consequences. It guides you through identifying decision-worthy choices, articulating constraints, evaluating options, and projecting impacts—ensuring future readers understand not just what was decided, but why.
ADR Writer creates formatted architecture decision records that capture the problem, alternatives weighed, and chosen solution. It automatically numbers files, slugifies titles, and populates a standard template to ensure design decisions survive team turnover.
This skill produces structured technical documentation across four types: architectural decision records for design choices, system overviews for onboarding, API references for integrations, and operational runbooks for procedures. It enforces anti-patterns like documentation drift and future fiction while matching detail to audience—from high-level concepts for new developers to procedural steps for operations teams.
Capture significant technical choices in a structured format that explains the problem, alternatives weighed, and reasoning behind your decision. Use the provided template to create numbered records in your docs folder, then reference them from code comments when relevant. This ensures your team understands not just what was decided, but why—making it easier to revisit or build on those choices later.
This skill generates Architecture Decision Records (ADRs) that capture the context, decision, and consequences of significant technical choices. It guides you through gathering essential information, selecting from three formats (MADR, Nygard, or Y-Statement), and produces a structured document that preserves reasoning for future engineers.
Adr helps you systematically capture architecture decisions with context, options, and consequences. Create numbered decision records, browse your decision history, and search past choices to avoid redundant deliberation.
More skills architecture-decision (MIT) · Architecture Decision Records (NOASSERTION) · Adr Architecture (unlicensed) · documentation-and-adrs (MIT) · architecture-decision-record (MIT) · documentation-and-adrs (MIT) · Technical Writing (unlicensed) · write-adr (Apache-2.0)