adr-writer — community adr-writer, engineering-knowledge-base, community, ide skills

v1.0.0

Sobre este Skill

Perfeito para Agentes de Desenvolvimento que necessitam de criação e gerenciamento explícito de Registros de Decisões de Arquitetura. Cria Architecture Decision Records (ADRs) para decisões técnicas. Inclui alternativas, justificativa e consequências.

LucasBiason LucasBiason
[1]
[0]
Updated: 3/20/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for teams, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
7/11
Quality Score
41
Canonical Locale
en
Detected Body Locale
en

Perfeito para Agentes de Desenvolvimento que necessitam de criação e gerenciamento explícito de Registros de Decisões de Arquitetura. Cria Architecture Decision Records (ADRs) para decisões técnicas. Inclui alternativas, justificativa e consequências.

Por que usar essa habilidade

Habilita os agentes a criar e documentar compensações e escolhas de design usando Registros de Decisões de Arquitetura (ADRs), fornecendo decisões explícitas e revisáveis para equipes de desenvolvimento, incluindo opções para padrões de arquitetura, armazenamento, autenticação e comunicação entre serviços.

Melhor para

Perfeito para Agentes de Desenvolvimento que necessitam de criação e gerenciamento explícito de Registros de Decisões de Arquitetura.

Casos de Uso Práticos for adr-writer

Documentar compensações de design para referência de desenvolvimento futuro
Criar ADRs para escolhas impactantes em CI/CD, observabilidade e consistência de dados
Revisar e atualizar ADRs existentes para requisitos de projeto em evolução

! Segurança e Limitações

  • Exige identificação de compensações de design significativas
  • Não é adequado para escolhas triviais
  • Os arquivos de saída são armazenados no diretório spec/90-decisions/

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is adr-writer?

Perfeito para Agentes de Desenvolvimento que necessitam de criação e gerenciamento explícito de Registros de Decisões de Arquitetura. Cria Architecture Decision Records (ADRs) para decisões técnicas. Inclui alternativas, justificativa e consequências.

How do I install adr-writer?

Run the command: npx killer-skills add LucasBiason/engineering-knowledge-base/adr-writer. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for adr-writer?

Key use cases include: Documentar compensações de design para referência de desenvolvimento futuro, Criar ADRs para escolhas impactantes em CI/CD, observabilidade e consistência de dados, Revisar e atualizar ADRs existentes para requisitos de projeto em evolução.

Which IDEs are compatible with adr-writer?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for adr-writer?

Exige identificação de compensações de design significativas. Não é adequado para escolhas triviais. Os arquivos de saída são armazenados no diretório spec/90-decisions/.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add LucasBiason/engineering-knowledge-base/adr-writer. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use adr-writer immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

adr-writer

Install adr-writer, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

ADR Writer

Purpose

Create Architecture Decision Records (ADRs) whenever:

  • A trade-off exists
  • Multiple viable options exist
  • A choice impacts future development

This skill makes decisions explicit, documented, and reviewable.

When to Use

  • Plan Lead or user identifies a design trade-off
  • Deciding: architecture patterns, storage, auth, inter-service communication, CI/CD, observability, data consistency

Do NOT use ADRs for trivial choices.

Output Files

  • spec/90-decisions/ADR-XXXX-<slug>.md

Rules

  1. Every ADR must include at least 2 alternatives.
  2. Must explicitly state why alternatives were rejected.
  3. Must list consequences (positive + negative).
  4. If decision depends on unknowns → mark ADR as PROPOSED not ACCEPTED.
  5. Keep ADRs short and actionable.

ADR Statuses

PROPOSED | ACCEPTED | SUPERSEDED | REJECTED

Process

Step 0 — Identify the Decision

Write a 1–2 sentence "decision statement".

Step 1 — Gather Options

List 2–4 realistic alternatives.

Step 2 — Evaluation Criteria

Define what matters: Cost, Complexity, Team familiarity, Performance, Security, Vendor lock-in, Operational burden.

Step 3 — Choose + Justify

Pick one, explain why.

Step 4 — Consequences

List: Immediate consequences, Long-term consequences, Migration impact (if any).

Template

ADR-XXXX — <Title>. Status: PROPOSED. Date, Decision owners. Context. Decision. Options Considered (Option A/B with Pros/Cons). Decision Rationale. Consequences (Positive, Negative, Operational, Security/Compliance, Migration). Open Questions (if any).

Habilidades Relacionadas

Looking for an alternative to adr-writer or another community skill for your workflow? Explore these related open-source skills.

Ver tudo

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

widget-generator

Logo of f
f

Gerar plugins de widgets personalizáveis para o sistema de feed do prompts.chat

flags

Logo of vercel
vercel

O Framework React

138.4k
0
Navegador

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Desenvolvedor