$ loading_
用于规划阶段创建与维护架构决策记录，自动检查重复性、完整性与相关参考信息。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "adr-workflow" 技能： 1. 下载 https://raw.githubusercontent.com/microsoft/devsquad-copilot/main/.github/plugins/devsquad/skills/adr-workflow/SKILL.md 2. 保存为 ~/.claude/skills/adr-workflow/SKILL.md 3. 装好后重载技能，告诉我可以用了
请为“将文件存储从本地磁盘迁移到 Azure Blob Storage”创建一份 ADR，检查是否与现有决策重复，判断当前应使用的 ADR 状态，补充相关 Microsoft 官方文档链接，并给出粗略 Azure 成本估算，最后检查内容是否完整。
一份结构完整的 ADR 草稿，包含决策背景、方案比较、状态建议、参考文档、成本估算与完整性检查结果。
请根据以下进展更新这份 ADR：方案已完成 PoC，通过安全评审，计划下季度上线。请判断状态是否应从 Proposed 改为 Accepted，并检查是否还缺少实施影响、回滚方案或成本说明。
更新后的 ADR 内容与状态建议，并列出仍需补充或修正的字段。
我们计划引入 Azure API Management。请先检查现有 ADR 中是否已有相同或相近决策；如果有，请指出差异并建议复用还是新建；如果没有，请生成一份新的 ADR 初稿，并附上相关 Microsoft 文档与大致成本范围。
重复性分析结果，以及复用建议或新的 ADR 初稿，附带文档依据与成本范围。
Before creating any ADR, check if an ADR already exists in the same domain.
If a Proposed ADR exists: recommend reviewing and accepting the existing one before creating a new one. If an Accepted ADR exists: if the decision has changed, use "Superseded by NNNN".
Options: [R] Review existing / [S] Supersede (create new ADR) / [C] Create separate (different domain).
If no existing ADR exists in the domain:
[A] Decision already made: ask for the final decision and options considered. Create with Accepted status (but recommend Proposed for team review).[B] Needs discussion: ask for options to consider. Create with Proposed status.Options preferably come from the user. Offer suggestions only if:
Never invent options from templates, generic READMEs, or placeholder content.
Microsoft Documentation (for decisions involving Microsoft/Azure services):
microsoft_docs_searchmicrosoft_docs_fetch for full content of relevant pagesAzure Cost Estimate (if Azure MCP Server is available):
azure/pricing when cost is a ranked priority or the user asks about pricingAzure Cloud Architect (if Azure MCP Server is available and the project deploys to Azure):
azure/cloudarchitect (design) for Azure architecture recommendationsazure/deploy (architecture diagram) for Mermaid topology diagram[S] Incorporate / [M] Modify first / [I] Ignoredocs/architecture/decisions/ADR-TEMPLATE.mdNNNN-domain.md (e.g., 0001-data-persistence.md)Before considering the ADR complete, verify:
If there are missing fields, request information from the user.
| Rationalization | Reality |
|---|---|
| "ADRs are overhead" | A 10-minute ADR prevents a 2-hour debate about the same decision six months later. |
| "The code is self-documenting" | Code shows what was built. It does not show why, what alternatives were rejected, or what constraints applied. |
| "We will document the decision later" | Decisions made without records get re-debated. Later never comes. |
| "Nobody reads ADRs" | Future agents read them to avoid re-deciding. Future engineers read them to understand context. |
| "This decision is obvious, no ADR needed" | Obvious decisions still have alternatives. Recording the reasoning prevents someone from proposing the discarded alternative later. |
帮助你创建、切换并检查代码分支，确保实现前遵循正确分支策略。
记录代理执行中的决策依据，并在代理交接时传递结构化上下文。