workflow-control-plane
Keep the host Workflow plane available and route concrete tasks to matching Ready Workflows. Automatically use enabled Workbench Roles for useful ordinary subtasks when no Ready Workflow matches; the user need not request a Role. Manage Workflows on request. Do not start Runs for planning, discussion, comparison, audit, or experiment design.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- workflow-control-plane
- description
- Keep the host Workflow plane available and route concrete tasks to matching Ready Workflows. Automatically use enabled Workbench Roles for useful ordinary subtasks when no Ready Workflow matches; the user need not request a Role. Manage Workflows on request. Do not start Runs for planning, discussion, comparison, audit, or experiment design.
02 资源文件 16
- 参考文档agents/openai.yaml209 B
- 参考文档references/architecture.md12.5 KB
- 参考文档references/authoring-cleanup.md4.4 KB
- 参考文档references/authoring-contract.md29.2 KB
- 参考文档references/authoring-parallel-cost.md12.2 KB
- 参考文档references/authoring-qualification.md29.6 KB
- 参考文档references/authoring-review.md6.8 KB
- 参考文档references/authoring.md5.9 KB
- 参考文档references/connection.md2.3 KB
- 参考文档references/editing.md2.2 KB
- 参考文档references/execution.md12.5 KB
- 参考文档references/native-execution.md6.6 KB
- 参考文档references/packages.md1.1 KB
- 参考文档references/parallel.md4.9 KB
- 参考文档references/provider-contracts.md11.3 KB
- 参考文档references/recovery.md3.5 KB
03 SKILL.md 正文
Workflow control plane
Automatic Roles are the default. When no Ready Workflow matches a concrete request and a helper would materially help, automatically select an enabled Workbench Role and launch its returned adapter. Follow Role orchestration.
The persistent control plane is available without a matching Workflow. Workflows cover end-to-end tasks; Roles assign ordinary helpers through the orchestration skill and never enter running Workflow nodes.
A failed Run is unfinished. On completion_satisfied:false or
recovery_required:true, inspect the failed node and evidence, repair or retry
that unit. Report completion only when final acceptance makes the Run succeeded.
Read the route for this request
Read only the relevant route; do not load authoring instructions into execution context.
- Exact Ready startup or node packet already supplied: call its named tool with the supplied business arguments and that tool's Host invocation preset. Follow the returned action. The tool and packet supply the execution contract; Host reads the supplied inputs_path and checks/registers dependencies during startup. No input-file reread, prepare_environment call, execution-reference read, tool inventory, capabilities call, listing or routing is required. Read a reference only for a missing detail or an observed failure.
- Execute an unselected concrete task: read execution to select its Ready Workflow and start it.
- Generate from a Skill or brief: read authoring. It links the semantic contract, independent review, and mandatory completion cleanup.
- Inspect, edit, publish or delete an existing Workflow: read editing.
- Export or install a Workflow package: read packages.
- Recover a failed/interrupted Run or its control: read recovery.
- Remove superseded authoring Drafts: read authoring cleanup.
- Unavailable tools or UI connection failures: read connection diagnosis.
- Meta: planning, comparing, auditing, evaluating, or designing experiments about Skills or Workflows. Work directly. Merely mentioning this plugin is not permission to start a Run.
Open UI with codex_agents_workflow_app or codex_agents_workflow_settings; no Run/thread is created. Use codex_agents_workflow_console for standalone or unsupported hosts. Keep transport/bootstrap out of model context. Report the observed error; never invent receipts, hide App failures or substitute execution.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.