Menu
Accept the active Goal or Cycle at its final pending acceptance gate. Use for /hw:accept or an explicit user acceptance statement.
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
Route project work through the manifest-based Hypo-Workflow protocol. Use for /hw:* commands, repository initialization, Goal or Cycle delivery, structured experiments, focused maintenance records, final acceptance, and restart-safe Resume.
Define and run a multi-stage Hypo-Workflow delivery with ordered Milestones and one final manual acceptance. Use for /hw:cycle or work whose stages have real dependency order.
Maintain a non-linear, reproducible experiment lane with project knowledge, run identity, parameter scans, long-run supervision, scientific review, immutable Git records, and instant materialized status. Use for /hw:experiment, experiment setup or reruns, NeRF/AceSim-style comparisons, baseline changes, parameter sweeps, result triage, and questions such as "现在实验怎么样".
Define and run one bounded Hypo-Workflow delivery outcome without fake Milestones. Use for /hw:goal or when the user wants one explicit acceptance target that a capable model can execute after approval.
Inspect the repository and recommend one available Hypo-Workflow path. Use for /hw:guide or when the user is unsure whether to initialize, use Goal, use Cycle, manage experiments, maintain, resume, accept, or reject.
Build an evidence-driven Goal Design or Cycle Plan. Use for /hw:plan and planning requests that need questions, architecture choices, ordered decomposition, or durable research before execution.
| name | accept |
| description | Accept the active Goal or Cycle at its final pending acceptance gate. Use for /hw:accept or an explicit user acceptance statement. |
用户可见内容遵循项目输出语言；缺失时跟随当前对话语言。内部 schema key 保持英文。
Require the active Delivery to be pending_acceptance. Build the exact delivery.accept Receipt context from current Runtime, issue the user-scoped Receipt through the host decision gate, then call store.accept.
Import Core from the installed bundle, pass the target workspace as root, and create Delivery/Receipt stores with the same explicit zero-argument Clock. Show the complete Receipt binding first; only after explicit user confirmation issue it, then call accept with a unique safe mutation { id }.
Reject stale plan, state, scope, actor, object, or reused Receipt bindings. Acceptance changes only final Delivery state to accepted; Cycle Milestones remain verified and have no individual acceptance state.
Explain the delivered result, verification evidence, remaining risks, and acceptance effect directly in chat.
