菜单
Draft a new ADR (Architecture Decision Record) at doc/adr/NNNN-<short-title>.md, using Michael Nygard's Context/Decision/Consequences/Alternatives pattern. Use when the user wants to record, write, draft, propose, or document an architecture decision. Status starts at proposed.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime --skill ad-adr命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Generate ARCHITECTURE.md at the repo root by scanning the code first, pre-filling layers/patterns/observability/deployment from observed signals, then asking only the genuine gaps. Use when the user wants to bootstrap, scaffold, generate, document, or audit ARCHITECTURE.md (system-level patterns and boundaries, paired with ADRs in doc/adr/).
Sweep completed plan files (tasks Status:done, specs Status:shipped, PRDs Status:superseded, ADRs Status:superseded or deprecated) out of the working tree and into git history via `git rm`. Use when the user wants to archive, clean, prune, or sweep done tasks / shipped specs / superseded PRDs / superseded or deprecated ADRs / completed legacy plan documents. Hard-delete-only — git history is the ledger, no in-tree archive subdirectory, no `CHANGELOG.md` (Rule
Run this skill when the user explicitly invokes `/ad-audit` or names it ("run ad-audit", "audit against the rules"), or asks for the maximum quality gate before work reaches the team ("adversarial audit", "rules audit", "maximum gate", "verify before I post", "exhaustive review"). Heavier and more exhaustive than `ad-review` (light two-axis diff review); distinct from `ad-drift` (documentation-drift only). Auto-trigger note: `allow_implicit_invocation: true` is set, so audit-language can fire the skill; if a request is ambiguous, confirm scope before invoking. Mechanical shape: ONE pass in the current session. The skill resolves the project's rule-set (repo binding docs plus optional curated machine and project rule layers), walks every rule-group as a checklist with structural separation, emits an explicit verdict for every rule (pass / violation / judgement-call / n-a — none skipped, so coverage is a matrix), grounds every finding on the actual code/output, and gates every teammate-visible claim on a real e
基于 SOC 职业分类
正在显示 SKILL.md
| name | ad-adr |
| description | Draft a new ADR (Architecture Decision Record) at doc/adr/NNNN-<short-title>.md, using Michael Nygard's Context/Decision/Consequences/Alternatives pattern. Use when the user wants to record, write, draft, propose, or document an architecture decision. Status starts at proposed. |
| summary | Draft a new ADR at `doc/adr/NNNN-<slug>.md`. |
<background_information>
Drafts doc/adr/NNNN-<short-title>.md for one architecture decision. Status lifecycle: proposed → accepted → deprecated | superseded by ADR-NNNN.
</background_information>
Step 2 — confirm scope. The ADR captures one decision. If the user's request implies multiple, ask which to write first; the others become follow-up ADRs.
Step 3 — fill from conversation only. Use the template below. Fill Context, Decision, Consequences, and Alternatives Considered from this conversation only — no fabrication. If a section has no signal, ask one question per gap.
Decision must be a directive ("We will…"), not a description.
Consequences lists positive and negative; do not balance for the sake of balance.
Alternatives Considered lists each rejected option with a one-line reason.
Step 4 — write the file. Path: doc/adr/<NNNN>-<short-slug>.md. Slug: kebab-case, ≤6 words. Status: proposed. Date: today, ISO format. Deciders: ask the user.
Stop after writing. Do NOT flip status to accepted — that requires user review.
<output_contract>
A single new file at doc/adr/<NNNN>-<short-slug>.md. Status proposed. No existing ADRs modified. No invented content.
ADRs are decision-record artifacts and are exempt from the no-dates rule (Documentation Discipline §2): **Status:** and **Date:** are required for Nygard supersession ordering. Remaining Documentation Discipline rules (WORKFLOW.md §2) apply at write time:
Context is the business-context-first section — forces and problem before the decision.Decision is a directive; rejected paths go in Alternatives Considered.
</output_contract>proposed; the user flips to accepted after review (the agent does not).ARCHITECTURE.md's Active ADRs list, add the entry there./ad-task for the work units that implement the decision./ad-drift periodically to confirm the decision still holds against the code.