メニュー
[UDS] Create, manage, and track Architecture Decision Records (ADR). Use when: architecture decisions, technology choices, design trade-offs, pattern selection. Keywords: ADR, architecture decision, decision record, trade-off.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/AsiaOstrich/universal-dev-standards --skill adrコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
SOC 職業分類に基づく
| name | adr |
| scope | universal |
| description | [UDS] Create, manage, and track Architecture Decision Records (ADR). Use when: architecture decisions, technology choices, design trade-offs, pattern selection. Keywords: ADR, architecture decision, decision record, trade-off. |
| allowed-tools | Read, Write, Glob, Grep |
| argument-hint | [create | list | supersede ADR-NNN | 決策主題] |
Language: English | 繁體中文
Create, manage, and track Architecture Decision Records. Capture the context, options, and rationale behind significant technical decisions.
建立、管理和追蹤架構決策記錄。捕捉重大技術決策的背景、選項和理由。
CAPTURE ──► ANALYZE ──► DECIDE ──► RECORD ──► LINK
捕捉背景 分析選項 做出決策 記錄 ADR 建立連結
Identify the context and constraints driving the decision.
識別驅動決策的背景與限制條件。
| Step | Action | 步驟 |
|---|---|---|
| 1 | Identify the problem or opportunity | 識別問題或機會 |
| 2 | List constraints (time, budget, team skills) | 列出限制條件 |
| 3 | Define decision drivers | 定義決策驅動因素 |
Explore at least 2 options with pros and cons.
至少探索 2 個選項，列出優缺點。
| Step | Action | 步驟 |
|---|---|---|
| 1 | Brainstorm candidate options | 腦力激盪候選方案 |
| 2 | Evaluate each against decision drivers | 根據決策驅動因素評估 |
| 3 | Document pros/cons for each | 記錄各方案優缺點 |
Select the best option and articulate the rationale.
選擇最佳方案並闡述理由。
Generate the ADR file following the standard template.
依照標準模板產生 ADR 檔案。
Cross-reference with related artifacts (SPECs, PRs, code).
與相關工件（規格、PR、程式碼）建立交叉引用。
| Write ADR | Skip ADR |
|---|---|
| Framework/library choice | Routine dependency update |
| API contract or data format | Bug fix within existing architecture |
| Deployment strategy change | Code style decision |
| Establishing new patterns | Trivial implementation choice |
Rule of thumb: If someone might ask "why?" in 6 months, write an ADR.
經驗法則：如果 6 個月後有人可能會問「為什麼？」，就寫一份 ADR。
Proposed ──► Accepted ──► Deprecated
│
└──► Superseded by ADR-NNN
| Status | Description | 說明 |
|---|---|---|
| Proposed | Under discussion | 討論中 |
| Accepted | Active, should be followed | 已接受，應遵循 |
| Deprecated | No longer relevant | 不再適用 |
| Superseded | Replaced by newer ADR | 已被新 ADR 取代 |
# ADR-NNN: [Title]
- Status: [Proposed | Accepted | Deprecated | Superseded]
- Date: YYYY-MM-DD
- Deciders: [people]
- Technical Story: [SPEC-ID or Issue]
## Context
## Decision Drivers
## Considered Options
## Decision Outcome
### Consequences (Good / Bad / Neutral)
## Links
docs/adr/
├── ADR-001-short-description.md
├── ADR-002-short-description.md
└── README.md # Index (optional)
| Command | Action | 說明 |
|---|---|---|
/adr | Interactive ADR creation wizard | 互動式建立 ADR |
/adr create | Create a new ADR | 建立新 ADR |
/adr list | List all ADRs with status | 列出所有 ADR 及狀態 |
/adr search [keyword] | Search ADRs by keyword | 依關鍵字搜尋 ADR |
/adr supersede [ADR-NNN] | Supersede an existing ADR | 取代現有 ADR |
/adr review | Review ADRs for staleness | 審查過期的 ADR |
| Skill | Integration | 整合方式 |
|---|---|---|
/sdd | Reference ADRs in Technical Design; suggest creating ADR for major decisions | 在技術設計中引用 ADR |
/code-review | Reference ADRs as design rationale during code review | 程式碼審查時引用 ADR |
/commit | Include ADR-NNN in commit footer for traceability | 提交時在 footer 加入 ADR 編號 |
/brainstorm | Feed brainstorm output into ADR option analysis | 腦力激盪結果作為 ADR 選項分析輸入 |
Before accepting an ADR:
| Check | Criteria | 標準 |
|---|---|---|
| ☐ Context | Clearly explains the problem | 清楚說明問題 |
| ☐ Options | At least 2 options considered | 至少考慮 2 個選項 |
| ☐ Drivers | Decision drivers explicitly listed | 決策驅動因素明確列出 |
| ☐ Consequences | Both good and bad outcomes | 包含正面與負面結果 |
| ☐ Links | Related artifacts referenced | 相關工件已引用 |
After /adr completes, the AI assistant should suggest:
ADR created. Suggested next steps:
- Execute
/sddto create a spec if the decision requires implementation- Execute
/committo commit the ADR file- Update related SPECs to reference this ADR
- Share with team for review if status is
Proposed
ADR 已建立。建議下一步：
- 執行
/sdd建立規格（若決策需要實作）- 執行
/commit提交 ADR 檔案- 更新相關規格以引用此 ADR
- 若狀態為
Proposed，分享給團隊審查
When the user invokes /adr, the AI assistant MUST:
docs/adr/ to determine next ADR numberdocs/adr/ADR-NNN-title.mdWhen the user invokes /adr list:
docs/adr/ directoryWhen the user invokes /adr supersede [ADR-NNN]:
Superseded by ADR-NNNSupersedes ADR-NNN to new ADR[UDS] 以 Claude 原生 Agent tool 编排多任务执行计划（DAG-based，无外部引擎）。 Use when: executing a plan.json file with parallel/sequential task dependencies. Keywords: orchestrate, plan, execute, DAG, task plan, 编排, 执行计划, 并行.
[UDS] 从 Spec 文档、OpenSpec 变更或自由文本需求生成 plan.json。 Use when: converting specifications into executable task plans for /orchestrate. Keywords: plan, spec, task plan, 计划, 规格, 任务, plan.json, DAG.
[UDS] AI 辅助 git push 安全层：质量门禁 + 协作护栏。 Use when: pushing commits, force pushing, pushing to protected branches, pushing feature branches. Keywords: git push, force push, protected branch, quality gate, push receipt, PR automation, 推送, 保护分支, 质量门禁.