Запись архитектурного решения (ADR)
Пишет короткую датированную запись архитектурного решения (ADR): контекст, решение, рассмотренные варианты с компромиссами, последствия и статус, и кладёт её рядом с кодом. Используйте, когда принято или обсуждается важное техническое решение, которое нужно зафиксировать.
architecture-decision-recordУстановка
Выполните одну команду — она сохранит SKILL.md в папку скиллов агента. Перезапустите агента, и он подхватит скилл сам.
mkdir -p ~/.claude/skills/architecture-decision-record && curl -fsSL https://anymodel.org/en/skills/docs/architecture-decision-record/SKILL.md -o ~/.claude/skills/architecture-decision-record/SKILL.md
mkdir -p ~/.agents/skills/architecture-decision-record && curl -fsSL https://anymodel.org/en/skills/docs/architecture-decision-record/SKILL.md -o ~/.agents/skills/architecture-decision-record/SKILL.md
New-Item -ItemType Directory -Force "$HOME\.claude\skills\architecture-decision-record" | Out-Null; Invoke-WebRequest https://anymodel.org/en/skills/docs/architecture-decision-record/SKILL.md -UseBasicParsing -OutFile "$HOME\.claude\skills\architecture-decision-record\SKILL.md"
New-Item -ItemType Directory -Force "$HOME\.agents\skills\architecture-decision-record" | Out-Null; Invoke-WebRequest https://anymodel.org/en/skills/docs/architecture-decision-record/SKILL.md -UseBasicParsing -OutFile "$HOME\.agents\skills\architecture-decision-record\SKILL.md"
Другой агент: сохраните файл в его папку скиллов или дайте ему ссылку на файл: https://anymodel.org/en/skills/docs/architecture-decision-record/SKILL.md
SKILL.md
Architecture Decision Record
An ADR explains why the code is the way it is, so a future reader does not have to guess or reverse the decision blindly. One decision per record. Short is a feature.
When to write one
Write an ADR when the choice is costly to reverse or will surprise a newcomer: a database, framework, queue, auth approach, API style, data model shape, build or deploy method, a deliberate rejection of the obvious option. Do not write one for routine implementation choices.
Workflow
- Find the existing convention. Look for
docs/adr/,docs/decisions/,adr/, or files named like0001-*.md. Follow its template, numbering and status vocabulary. If none exists, createdocs/adr/with0001-<slug>.mdand ask the user before introducing the folder. - Gather the real context. Read the code and recent history related to the decision (
git logon the files, issue or PR text if the user provides it). Ask the user for facts only they know: constraints, deadlines, team skills, budget, what was already tried. Do not invent the reasoning. - List at least two real options, including "do nothing" or the status quo when it is genuine. For each, note honest advantages and drawbacks. Include the option that was rejected and the real reason.
- State the decision in one or two plain sentences in active voice: "We will use PostgreSQL for ...".
- Write consequences: what gets easier, what gets harder, new obligations (migrations, monitoring, training), and what would make us revisit the decision.
- Set the status and the date (today's date in
YYYY-MM-DD). Link related ADRs. - Keep it to about one page. Confirm facts with the user before finalizing, because an ADR with wrong rationale does lasting harm.
Template
# 0007. Use PostgreSQL for order storage
Date: 2026-03-14
Status: Accepted (Proposed | Accepted | Deprecated | Superseded by 0012)
## Context
The situation and forces: requirements, constraints, scale, team skills, what
triggered the decision. Facts, not opinions.
## Decision
We will ...
## Options considered
1. PostgreSQL - relational, transactions, team knows it; needs a managed instance
2. SQLite - zero ops; single writer limits concurrent writes
3. Document store - flexible schema; weaker joins for reporting
## Consequences
- Good: ...
- Bad / costs: ...
- Revisit when: write volume exceeds ..., or the hosting plan changes.
Rules
- Present tense for the decision, past tense for history. Write for someone reading in two years.
- Do not rewrite accepted ADRs. If the decision changes, write a new ADR, mark the old one "Superseded by NNNN", and link both ways.
- Record trade-offs honestly, including the downsides of the chosen option. Avoid selling it.
- Numbers beat adjectives: "p95 under 200 ms at 50 requests per second" instead of "fast".
- Do not include secrets, internal hostnames or personal data.
- Store it in the repository next to the code it concerns, and commit it with or right after the change.
Pitfalls
- Documenting a decision after the fact without telling the reader that it is retrospective; say so in the context.
- A single option dressed up as a comparison. If there was no alternative, the decision may not need an ADR.
- Mixing several decisions in one record.
- Vague consequences such as "improves maintainability" with no concrete effect.
- Leaving status as Proposed after the change shipped.
Report back
The path of the file written, the one-line decision, the options listed, and the facts you assumed that the user should confirm.
Source: AnyModel skills catalog · License: CC BY 4.0
Подключить через AnyModel API
Скилл работает на той модели, которую использует агент. Подключите Claude Code, Codex или Cursor к AnyModel и запускайте его на Claude, GPT, Gemini и других моделях по одному ключу — оплата за токены, без подписки.
AnyModel