Honor task boundaries without category-based reconfirmation
Plugin-Submission: 376a2e62cb9798570173a95497ab405cf980872a40c3c42f358d083c5af2d63c
This commit is contained in:
1 parent
d1dabc10f6
commit
8e753e7204
7 files changed
+23
-5
No files matched your search
@@ -8,4 +8,4 @@ This repository maintains a Codex skill and an optional global prompt template.
|
||||
- After changes run python3 -m unittest discover -s tests -v and python3 scripts/check_repository.py. Run the installed skill-creator validator when available.
|
||||
- Use synthetic fixtures only for deterministic parser/contract tests. Mark scenario reviews as static; live subagent behavior requires actual authorized tool calls.
|
||||
- Keep readme.md installation, rollback and compatibility notes aligned with behavior. Shared evidence schema changes require parser, tests and examples to move together.
|
||||
- Established repositories use a feature branch and PR; never merge or force-push without authorization. An explicitly requested empty-repository bootstrap may initialize its default branch.
|
||||
- Established repositories use a feature branch and PR. Determine execution scope from the user's task and stated boundaries; task-required pushes, merges and releases need no additional category-based approval. Honor higher-priority host restrictions and preserve the boundary against unauthorized force-pushes. An explicitly requested empty-repository bootstrap may initialize its default branch.
|
||||
@@ -41,6 +41,9 @@ These are static review cases, not a record that a model executed them. Use them
|
||||
| API supports configuration_update, Desktop tool lacks it | No claimed runtime effort switch or invented tool parameter |
|
||||
| API request uses automatic compaction and requests dynamic effort | Resolve documented incompatibility before enabling configuration updates |
|
||||
| Stronger instruction following encounters a vague skill suggestion | Identify the actual rule; do not invent an approval gate |
|
||||
| User requests a change through merge and release, with stated task boundaries | Parent completes task-required external steps within those boundaries; no separate category-based approval or reconfirmation |
|
||||
| User requests a local fix and explicitly forbids push or deployment | Honor the stated boundary; complete local work only |
|
||||
| Task-required production write has a materially ambiguous target | Clarify the target while continuing independent work; honor higher-priority host restrictions |
|
||||
| Small change passes relevant required checks | Stop validation unless new changes/failures/uncertainty justify more |
|
||||
| Active prompt grants standing parallel authorization; ordinary task has independent useful slices | Dispatch promptly without asking again; parent advances critical path |
|
||||
| Template merely exists on disk, no active delegation authorization | No spawn based solely on the template's existence |
|
||||
|
||||
@@ -0,0 +1,13 @@
|
||||
# 2.3.1 — 以任务边界执行,取消类别二次确认
|
||||
|
||||
## 变化
|
||||
|
||||
- 可选全局 `prompts/AGENTS.md` 以用户任务请求及其中声明的边界确定执行范围。完成任务所必需的外部写入、发布、合并、部署和生产写入随任务执行,不再因操作类别另设授权或二次确认。
|
||||
- 仓库开发约定与技能入口同步说明这一规则;只有目标或边界存在实质歧义时才澄清,更高优先级宿主限制继续生效。
|
||||
- 新增静态行为场景,覆盖任务包含合并发布、用户明确禁止外部步骤,以及生产目标存在实质歧义。
|
||||
|
||||
## 兼容与验证边界
|
||||
|
||||
子智能体触发授权、主线程串行处理外部步骤、所选模型、证据 schema、安装备份及破坏性操作边界保持原样。这是任务范围的解释调整,不授予超出用户任务的操作权限,也不覆盖宿主限制。
|
||||
|
||||
本地更新时先预览技能差异。已有个人全局规则应只修改对应条款并备份;`--include-prompt --apply` 仍会整体替换全局提示词,不用于合并个人规则。
|
||||
+1
-1
@@ -6,7 +6,7 @@
|
||||
|
||||
- 行动请求直接实施并完成验收,不停在计划或“可以帮忙”。解释、审查、诊断默认只读;修改请求包含范围内的本地编辑与验证。
|
||||
- 沿用已有授权,自行解决可逆的常规选择。只有答案实质影响结果或权限时才澄清,同时推进不依赖答案的已授权工作。
|
||||
- 外部写入、购买、发布、合并、部署、生产写入与难恢复的破坏性操作须明确授权;先确定目标并完成不依赖该授权的准备工作。
|
||||
- 以用户任务请求及其中声明的边界确定执行范围;完成任务所必需的外部写入、发布、合并、部署和生产写入随任务执行,不因操作类别另设授权或二次确认。只有目标或边界存在实质歧义时才澄清;更高优先级宿主限制仍须遵守。
|
||||
- “继续”“完成”不扩大权限。补充要求默认修正当前目标,状态查询不取消任务;明确取消或替换目标时停止失效操作。
|
||||
|
||||
## 2. 证据、技能与边界
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Codex Subagent Router
|
||||
|
||||
当前版本:**2.3.0**。Sol 首选升级为 GPT-6.1 Sol,适配原生 Multi-agent beta 和请求兼容边界,保留 Luna 舰队、Astra 按需介入、滚动调度及证据裁决。见 [2.3 发行说明](docs/releases/2.3.0.md)、[舰队调度](skills/codex-subagent-router/references/fleet.md) 和 [专家介入与裁决](skills/codex-subagent-router/references/escalation.md)。
|
||||
当前版本:**2.3.1**。执行范围以用户任务及所述边界为准,任务必需的发布、合并、部署等不再因操作类别触发二次确认。保留 GPT-6.1 Sol 首选路由、Luna 舰队、Astra 按需介入及原生 Multi-agent 兼容边界。见 [2.3.1 发行说明](docs/releases/2.3.1.md)、[2.3 发行说明](docs/releases/2.3.0.md)、[舰队调度](skills/codex-subagent-router/references/fleet.md) 和 [专家介入与裁决](skills/codex-subagent-router/references/escalation.md)。
|
||||
|
||||
面向 **GPT-6 Luna / GPT-6.1 Sol / GPT-6 Astra** 的 Codex 路由技能与工程提示词。把可独立完成的工作交给合适的模型,并让触发、运行状态、证据与最终责任保持清楚。Terra 已退出推荐与自动回退路线;旧宿主按实际能力显式兼容。
|
||||
|
||||
|
||||
@@ -5,10 +5,12 @@ description: Route authorized Codex subagents across GPT-6 Luna, GPT-6.1 Sol and
|
||||
|
||||
# Codex Subagent Router
|
||||
|
||||
Version 2.3.0. For new general engineering sessions recommend GPT-6.1 Sol / medium, with high for demonstrated reasoning needs. Preserve the selected parent. Use Astra proactively for high-leverage difficult decisions, independent counterexample reviews and residual hard reasoning when its depth adds value over Sol; neither prior failure nor a model quota is required.
|
||||
Version 2.3.1. For new general engineering sessions recommend GPT-6.1 Sol / medium, with high for demonstrated reasoning needs. Preserve the selected parent. Use Astra proactively for high-leverage difficult decisions, independent counterexample reviews and residual hard reasoning when its depth adds value over Sol; neither prior failure nor a model quota is required.
|
||||
|
||||
Make delegation useful, observable and bounded. Preserve the selected parent model. The parent owns the critical path, shared decisions, integration and final acceptance. This skill neither changes configuration nor grants external permissions.
|
||||
|
||||
Determine execution scope from the user's task and stated boundaries. The parent carries out task-required external writes, publication, merges, deployment and production writes without adding a category-based approval or reconfirmation gate. Clarify only material ambiguity in the target or scope, and honor higher-priority host restrictions. Delegation authorization and parent ownership remain unchanged.
|
||||
|
||||
## Trigger before routing
|
||||
|
||||
Classify the request before using child tools:
|
||||
|
||||
Reference in new issue
Block a user