菜单
plcopen 已知边界（KB）登记流程——新核相对标准/旧线的行为边界如何编号与记录。Use when a change declares a behavior boundary, a deliberate deviation, or an explicit unsupported combination.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | plcopen-kb-boundary |
| description | plcopen 已知边界（KB）登记流程——新核相对标准/旧线的行为边界如何编号与记录。Use when a change declares a behavior boundary, a deliberate deviation, or an explicit unsupported combination. |
KB 条目是新核对外承诺的边界宣告：相对 PLCopen 标准的裁剪、相对 v0.x 的
修订、显式 unsupported 的组合、声明变更。注册表在
doc/compliance/known-boundaries.md（单一事实源，README 只留指针）。
doc/compliance/xxx.md、plcopen_core_xxx_tests）。// KB-036），让边界可从代码反查。写完自问：一个没读过本仓库的集成商，凭这一条能否判断"我的用法在不在 边界内、越界会看到什么错误码"？不能就补。
plcopen 对抗性探测轮——系统性猎杀未声明缺陷（KB-051 方法论流程化）。Use when a milestone closes, when the maintainer questions a capability claim, or when auditing semantic parity across domains.
plcopen 提交前门禁——全量测试、RT 扫描、回放校验的准确命令与已知误报坑。Use before any commit/push in this repo, when the user says 门禁/gates, or when another skill finishes an implementation step.
plcopen 提交信息格式——angular 类型 + 中文四段正文 + KB/声明变更标注 + AI 声明。Use when committing in this repository.
plcopen 出处纪律——禁止来源清单与外部代码/文档引入规则。Use before referencing external implementations, vendoring third-party content, or writing planner/OTG/blending algorithms.
plcopen 新特性/新语义的规格先行全流程（语义矩阵 → 人批 → 测试先行 → 门禁 → 文档同步）。Use when adding any new capability, FB semantics, planner behavior, or when the user proposes a feature touching core/.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".