用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Maestra-Tech/ContextDevKit --skill source-command-new-adr命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | source-command-new-adr |
| description | Generate, validate, and explicitly accept a canonical ContextDevKit ADR. |
Use this skill when the user asks to run the migrated source command new-adr.
Create a canonical Authoritative Decision Record for: $ARGUMENTS
node contextkit/tools/scripts/decision.mjs search --objective "<key terms from the title>" --json.
If an accepted ADR already governs the choice, use it or supersede it; never
create a duplicate.0b. Deliberation is conditional [ADR-0158]. An explicit /debate, a
governed needsDebate: true classification, or a requirement in the selected
workflow/skill requires the council before this material decision is finalized.
Outside those triggers, deliberation is optional. Routing recommends the
executor; missing legacy receipt fields never cancel an activated council.
Resolve the fleet-safe next ADR id with
node contextkit/tools/scripts/intake-collision-gate.mjs --json; use the
ADR row's fleet value. Do not infer the id from one directory.
Classify the owner and decision before writing:
--context-type business + --primary-context BIZ-#### for a Business decision;--context-type operation + --primary-context OP-#### for an Operation decision;--context-type platform for standing platform governance.Choose one closed --kind and, when relevant, one closed --value-intent.
Preview, then create only through the canonical generator:
node contextkit/tools/scripts/decision.mjs create --id ADR-#### --kind ARCHITECTURE --context-type operation --primary-context OP-#### --title "$ARGUMENTS" --json
node contextkit/tools/scripts/decision.mjs create --id ADR-#### --kind ARCHITECTURE --context-type operation --primary-context OP-#### --title "$ARGUMENTS" --apply --json
Never copy contextkit/memory/decisions/_TEMPLATE.md, hand-build front matter,
or create a new legacy ADR. Fill the generated guidance without changing its
machine schema, documentVersion, or required headings.
Validate the exact file with
node contextkit/tools/scripts/decision.mjs validate --file <path> --json.
Show the proposed ADR to the user. Only an explicit human decision authorizes:
node contextkit/tools/scripts/decision.mjs accept --id ADR-#### --actor human --apply --json.
Acceptance stamps the deterministic decision hash; never hand-edit it.
Link the accepted ADR to the governing Business, Operation, or Workflow JSON
with decision.mjs link. Preview implied work with
node contextkit/tools/scripts/adr-tasks.mjs <NNNN> --json; this is
preview-only and never creates task authority. If implementation is accepted,
add tasks only through the named canonical workflow/batch pipeline/tasks.json.
ADR creation never seeds tasks or dispatches agents automatically.
To change an accepted ADR, generate a new one and use the canonical supersession lifecycle. Never delete or rewrite an accepted record.