Идеально подходит для агентов разработки, которым требуется явное создание и управление Записями об архитектурных решениях. 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: Документирование компромиссов дизайна для будущей ссылки разработки, Создание ADR для влиятельных выборов в CI/CD, наблюдаемости и согласованности данных, Просмотр и обновление существующих ADR для развивающихся требований проекта.

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

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

Name: adr-writer
Availability: InStock
Author: LucasBiason

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

Every ADR must include at least 2 alternatives.
Must explicitly state why alternatives were rejected.
Must list consequences (positive + negative).
If decision depends on unknowns → mark ADR as PROPOSED not ACCEPTED.
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).

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

Об этом навыке

Killer-Skills Review

Зачем использовать этот навык

Подходит лучше всего

↓ Реализуемые кейсы использования for adr-writer

! Безопасность и ограничения

Why this page is reference-only

Source Boundary

Decide The Next Action Before You Keep Reading Repository Material

Start With Installation And Validation

Cross-Check Against Trusted Picks

Move To Workflow Collections For Team Rollout

Browser Sandbox Environment

⚡️ Ready to unleash?

FAQ & Installation Steps

? Frequently Asked Questions

What is adr-writer?