菜单
Plan an Elsa replacement-contract implementation before coding. Use when exactly one implementation should be active per app/runtime context, when adding or replacing a single-implementation service, or when checking conflict detection for replacement contracts.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/elsa-workflows/elsa-foundation --skill elsa-add-replacement-contract命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Review a branch or pull request to convergence with independent reviewers and adversarial verification, then merge only on a fully green gate with evidence posted as a PR comment. Use when a branch or PR is ready for review, when review fixes need re-reviewing, or when a user asks to review and merge.
Refresh or plan refreshes for generated Elsa maps. Use when map inputs changed, map freshness is uncertain, extension-point catalogs changed, project/package references changed, specs changed, or another skill needs current navigation facts.
Execute the implementation planning workflow using the plan template to generate design artifacts.
基于 SOC 职业分类
正在显示 SKILL.md
| name | elsa-add-replacement-contract |
| description | Plan an Elsa replacement-contract implementation before coding. Use when exactly one implementation should be active per app/runtime context, when adding or replacing a single-implementation service, or when checking conflict detection for replacement contracts. |
| argument-hint | Replacement contract scenario |
| compatibility | Requires elsa-foundation constitution, docs, and extension-point catalogs |
| metadata | {"author":"elsa-foundation","source":"docs/skills/catalog.md#add-replacement-contract-implementation"} |
| user-invocable | true |
| disable-model-invocation | false |
$ARGUMENTS
docs/skills/catalog.md#add-replacement-contract-implementation.IEnumerable<T> semantics.Do not implement until the user approves the plan. After approval, required tests, extension-point catalog updates, generated-map refreshes, and small docs follow-through are part of completing the approved work.