القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
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.
Resume the active manifest-based Hypo-Workflow Delivery from Runtime, Continuation, and the latest valid Recovery Pack. Use for /hw:resume or when tracked Goal/Cycle work must continue after restart or compaction.
| name | cycle |
| description | 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. |
用户可见内容遵循项目输出语言；缺失时跟随当前对话语言。内部 schema key 保持英文。
A Cycle is a peer Main Delivery, not a wrapper around Goal.
Use the Root Core Call Contract: import from the installed bundle, pass the target workspace as root, create the store with an explicit zero-argument Clock, and give every mutation a unique safe { id }. Issue transition Receipts only after the host has shown the full binding and received explicit user confirmation.
compileCyclePlan.proposeCycle; approval moves only to waiting_to_start.execution.worker_routing.mode without changing role separation: off omits hints, advisory records fallback, and required blocks an unsupported semantic handoff.pending_acceptance, then route one Cycle-level manual gate to /hw:accept or /hw:reject.Revision creates Feedback plus a superseding Plan Record, resets revised Milestones to pending, and requires renewed approval and explicit start.
Completion chat includes the change summary, technical approach, modified modules, test design, validation result, expected behavior, encountered problems, and remaining risks. New-format Records replace legacy Knowledge Ledger archival; never write or delete legacy .pipeline/knowledge/ from this Skill.