跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
设计与 UI

ln-24-architecture-decision-recorder

Records one architecture decision with alternatives, consequences and status; does not design the whole system.

levnikolaevich · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add levnikolaevich/claude-code-skills --skill ln-24-architecture-decision-recorder

技能说明


name: ln-24-architecture-decision-recorder description: "Records one architecture decision with alternatives, consequences and status; does not design the whole system."

Architecture Decision Recorder

Goal: Preserve the context, forces, alternatives, decision, and consequences of one architecturally significant choice in a compact durable record. Change only approved decision documentation; do not design the whole system, approve a decision silently, delete history, audit code, or implement the choice.

Execution contract: The ordered checkboxes are the Definition of Done. Track every item internally as PENDING, PROVEN with concrete evidence, CLEARED with evidence that its condition is absent, or UNPROVEN with a gap; reading, delegation, or tool failure is not proof. Reconcile items after each section. Before returning, resolve all PENDING and count only PROVEN and CLEARED; apply the skill's verdict and approval rules to every gap. Preserve user intent, scope, and existing authorization. Continue authorized work; ask only for consequential unresolved choices or required external approval. Scale depth to material risk without silently skipping checks. Preserve dependency and safety ordering; otherwise choose the verification method appropriate to each obligation. Treat equivalent user or repository evidence as valid input; another skill, named artifact, or complete lifecycle is not a prerequisite. Preserve source requirement and decision identifiers when available. Bind reused evidence to the relevant source version, dirty changes, configuration, and environment; invalidate only affected claims after a change. On continuation, reconcile the task, existing authorization, current state, and unresolved evidence before resuming. For long work, return a compact continuation record or update an already authorized task artifact; read-only skills do not persist it. Distinguish artifact readiness, verified behavior, and authority to perform an external action. Prepare authorized work before any required approval. If an instruction prevents progress, identify its exact source and explain the unresolved boundary; do not invent an approval gate from general caution.

Tool Routing

NeedPreferred capabilityFallback
Existing decision conventionRepository search and direct document readsUse the default path and compact format
Decision driversRequirements, architecture artifacts, implementation evidence, and stakeholder statementsMark unsupported drivers UNKNOWN
Alternatives and external claimsRepository evidence plus current official sourcesMark time-sensitive claims UNVERIFIED
Sequence and supersessionExisting filenames, indexes, and decision linksReturn BLOCKED rather than reuse a number
Document mutationMinimal patch to one approved decision record and necessary supersession linksReturn BLOCKED if authority or path is unclear

One record captures one decision. If the request contains independent decisions with different drivers or lifecycles, split them only with explicit approval.

Artifact Rules

  • Reuse the repository's established ADR convention when one exists.
  • Otherwise use docs/architecture/decisions/NNNN-<slug>.md with the next unused monotonic number.
  • Never renumber, delete, or rewrite the decision and rationale of historical records. Permit scoped status and supersession-link updates under the rules below; distinguish evolving proposed drafts from accepted history.
  • Default a new record to Proposed.
  • Use Accepted only after explicit confirmation from an authorized decision-maker.
  • A proposed replacement links to the current decision without changing its effective status. Mark the old record Superseded and link both directions only after the replacement is explicitly accepted; preserve historical content.
  • Keep the record short enough to review as a single decision.
  • Preserve the rationale a future maintainer needs to reconsider it safely.
  • Label retrospective records explicitly; do not imply that documentation created after implementation was prior approval.
  • Separate evidence needed before acceptance from monitoring required after adoption.
  • Prefer stable repository references over conversation, branch-local, or ephemeral links.

Checklist

1. Establish the Decision Contract

  • Resolve the exact decision, scope, owner or deciders, affected system, and why the choice is architecturally significant.
  • Read repository instructions, Git state, and existing decision conventions.
  • Search for duplicate, conflicting, deprecated, or superseding decisions before allocating a new record.
  • Confirm the request is one decision rather than a broad design or implementation plan.
  • Resolve the approved status; default to Proposed when acceptance is not explicit.

2. Gather Context and Forces

  • State the current context and problem in value-neutral language.
  • Extract business drivers, quality attributes, constraints, assumptions, and decision horizon from available evidence.
  • Identify affected boundaries, contracts, data, security, operations, cost, ownership, and migration implications.
  • Separate present facts from forecasts and preferences.
  • Record contradictions or missing evidence that could change the choice.

3. Evaluate Alternatives

  • Include the status quo and the simplest credible option unless they are demonstrably infeasible.
  • Include materially different alternatives rather than cosmetic variants.
  • Compare options against the same drivers: correctness, quality targets, complexity, reversibility, cost, operations, team fit, and evolution.
  • State why each rejected alternative loses in this context without claiming universal inferiority.
  • Record sensitivity or review triggers that would make a rejected option preferable later.

4. Record the Decision

  • Write titl
阅读完整来源 ↗