adr-writer — community adr-writer, engineering-knowledge-base, community, ide skills, Claude Code, Cursor, Windsurf

v1.0.0
GitHub

このスキルについて

開発エージェントが明示的なアーキテクチャ決定レコードの作成と管理を必要とする場合に最適です。 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 operators, 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

開発エージェントが明示的なアーキテクチャ決定レコードの作成と管理を必要とする場合に最適です。 Cria Architecture Decision Records (ADRs) para decisões técnicas. Inclui alternativas, justificativa e consequências.

このスキルを使用する理由

エージェントがアーキテクチャ決定レコード（ADRs）を使用してトレードオフと設計上の選択を文書化できるようにし、開発チームに明確かつレビュー可能な決定を提供します。アーキテクチャパターン、ストレージ、認証、およびサービスの間の通信のオプションなどが含まれます。

おすすめ

開発エージェントが明示的なアーキテクチャ決定レコードの作成と管理を必要とする場合に最適です。

↓ 実現可能なユースケース for adr-writer

将来の開発の参考として設計上のトレードオフを文書化する
CI/CD、可観測性、データ一貫性などの重要な選択に対してADRsを作成する
プロジェクトの要件が変化するにつれて既存のADRsをレビューして更新する

! セキュリティと制限

  • 重要な設計上のトレードオフを特定する必要がある
  • 些細な選択には適さない
  • 出力ファイルは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.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
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?

開発エージェントが明示的なアーキテクチャ決定レコードの作成と管理を必要とする場合に最適です。 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. 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: 将来の開発の参考として設計上のトレードオフを文書化する, CI/CD、可観測性、データ一貫性などの重要な選択に対してADRsを作成する, プロジェクトの要件が変化するにつれて既存のADRsをレビューして更新する.

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?

重要な設計上のトレードオフを特定する必要がある. 些細な選択には適さない. 出力ファイルは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. 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. Works with Claude Code, Cursor, and Windsurf with one-command setup.

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).

関連スキル

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

すべて表示

openclaw-release-maintainer

Logo of openclaw
openclaw

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

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

カスタマイズ可能なウィジェットプラグインをprompts.chatのフィードシステム用に生成する

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

React フレームワーク

★ 138.4k
⑂ 0
ブラウザ

pr-review

Logo of pytorch
pytorch

Pythonにおけるテンソルと動的ニューラルネットワーク（強力なGPUアクセラレーション）

★ 98.6k
⑂ 0
開発者