计划执行与检查节点
executing-plans
按既定实施计划完成工作,保持过程检查和反馈。
od-new-generation【效率与协作】Default reference pipeline for the new-generation taskKind — discovery → plan → generate → critique with a critique-theater devloop.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Spec §10.1 / §23.3.3: when a plugin omits od.pipeline, the daemon
falls back to this scenario plugin's pipeline. Replacing the
default for an enterprise / vertical edition is now a content edit
rather than a code change.
{
"stages": [
{ "id": "discovery", "atoms": ["discovery-question-form"] },
{ "id": "plan", "atoms": ["direction-picker", "todo-write"] },
{ "id": "generate", "atoms": ["file-write", "live-artifact"] },
{
"id": "critique", "atoms": ["critique-theater"],
"repeat": true,
"until": "critique.score>=4 || iterations>=3"
}
]
}
The discovery stage gives the agent a clean surface for clarifying questions; the plan stage commits to a TodoWrite-backed plan; the generate stage produces the artifact; the critique stage devloops until the score converges or the iteration ceiling is hit.
A plugin can override or extend by declaring its own od.pipeline.
The default applies only when the plugin's pipeline is absent.