Menu
plcopen harness 与文档体系的路由索引。
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | plcopen-guide |
| description | plcopen harness 与文档体系的路由索引。 |
| disable-model-invocation | true |
| 场景 | 技能 |
|---|---|
| 加新特性/新语义 | plcopen-semantic-feature（全流程），实现环节配 tdd |
| 提交/推送前 | plcopen-gates → plcopen-commit-style |
| 回放红了 / 想改基线 / 加语料 | plcopen-replay-baseline |
| 写/改周期路径代码 | plcopen-rt-safety |
| 声明行为边界 | plcopen-kb-boundary |
| 引外部代码/写算法前 | plcopen-provenance |
| 难查的 bug / 性能回归 | diagnosing-bugs |
| 评审一段 diff | code-review |
| 设计模块接口 | codebase-design，需要探索用 prototype |
| 压测一个计划 | grilling / grill-me |
| 拆计划为任务 | to-prd → to-issues（tracker = 拆解文档任务表） |
| 会话交接 | handoff |
| 写新技能 | writing-great-skills |
| 层 | 位置 | 回答 |
|---|---|---|
| 共同语言 | CONTEXT.md | 术语什么意思 |
| 现状 | STATUS.md | 现在能干什么、进行到哪 |
| 规格（normative） | doc/compliance/（矩阵 + known-boundaries.md） | "做到"的定义、边界在哪 |
| 决策 | doc/design/decisions/（ADR） | 为什么这样设计 |
| 计划 | doc/planning/（仅现行） | 接下来做什么、代价多少 |
| 历史 | doc/archive/、doc/vision/ | 当年为什么那样 |
| 硬规则 | CLAUDE.md / AGENTS.md | AI 的红线与权限 |
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".
