메뉴
plcopen 新特性/新语义的规格先行全流程（语义矩阵 → 人批 → 测试先行 → 门禁 → 文档同步）。Use when adding any new capability, FB semantics, planner behavior, or when the user proposes a feature touching core/.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
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".
plcopen harness 与文档体系的路由索引。
| name | plcopen-semantic-feature |
| description | plcopen 新特性/新语义的规格先行全流程（语义矩阵 → 人批 → 测试先行 → 门禁 → 文档同步）。Use when adding any new capability, FB semantics, planner behavior, or when the user proposes a feature touching core/. |
新特性 = 新语义。未定义的语义组合显式报错，不静默猜测。流程六步， 每步有完成判据：
doc/compliance/ 写语义矩阵（体例参照
part4-lookahead-semantics.md）：定位与不变量表（哪些既有合同不动）、
决策点表（提案 + 理由）、退化与拒绝规则表（显式，进验收测试）、
验收指标表（纯软件可验证 + 门槛数字）、不做清单。标注状态
草案，待维护者批准。提交。
完成判据：五个表齐全，每条拒绝规则可写成测试。已批准（日期 + 范围）——批准记录进
文档，不留在会话里。core/test/*_tests.cpp，
plain-main + fail() 体例，CMake add_test 接线）。跑红确认。
完成判据：测试红且失败点是预期断言。plcopen-rt-safety。规划器/执行器变更必须过回放
（plcopen-replay-baseline）。plcopen-gates 全绿。doc/compliance/known-boundaries.md 加 KB 条目
（plcopen-kb-boundary）；CHANGELOG；模块 README；拆解文档状态。
提交用 plcopen-commit-style（提交信息引用已批准矩阵与门禁证据）。反模式：跳过步骤 2 直接实现；把多个语义决策藏在实现里而不进矩阵； 验收指标写成"能跑就行"。