菜单
Create a concise ADR for a durable, consequential architectural decision. Use when a significant, hard-to-reverse technical decision needs recording with context, alternatives, and consequences. Not for routine or easily reversible choices.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Eckii24/dotfiles --skill create-architectural-decision-record命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Fetch public URLs/articles/docs/blogs and save clean Markdown with source URL, headings, lists, links, and code blocks. Use when the source is a URL. Not for converting local files (use markitdown) or condensing/summarizing content (use the /summarize-article prompt).
Initialize state-of-the-art greenfield Python projects with current stable Python, uv, uv_build, Ruff, ty, pytest, a src layout, locked dependencies, and CI. Use when creating a new Python library, packaged application, CLI, service, worker, or standalone script.
Sharp professional roast-style critique for code, architecture, docs, UI, specs, plans, prompts, or ideas when user asks for brutal feedback. Not for actionable line-level code review (use code-review-excellence) or interactive plan interrogation (use grill-me).
基于 SOC 职业分类
正在显示 SKILL.md
| name | create-architectural-decision-record |
| description | Create a concise ADR for a durable, consequential architectural decision. Use when a significant, hard-to-reverse technical decision needs recording with context, alternatives, and consequences. Not for routine or easily reversible choices. |
Use only for a durable, consequential choice with considered alternatives and costly reversal. Keep ordinary implementation decisions in the spec, plan, code, or review evidence.
Derive context, decision, alternatives, and consequences from the task and existing artifacts. Read .ai/current-work.md and related artifacts when the decision originated in tracked work. Ask only for critical missing information; do not invent rationale, alternatives, or stakeholders.
Use a task-provided path. Otherwise use docs/adr/ relative to the repository only when that directory or its convention exists; otherwise ask where to save it. Follow the repository's existing ADR naming convention. Do not write outside the repository root.
Follow the local ADR convention. If none exists, use this minimal format:
# ADR-<nnn>: <decision title>
- **Status**: proposed | accepted | superseded
- **Date**: YYYY-MM-DD
## Context
[Constraint or problem that makes this decision necessary.]
## Decision
[Chosen direction and rationale.]
## Consequences
[Benefits, costs, and follow-up constraints.]
## Alternatives considered
- [Alternative] — [why not chosen]
Use concise, precise language. Preserve real rationale and rejected alternatives. ADRs are append-only history: supersede old ADRs; do not rewrite them.
project-memory — tracked-work context and archive rules.