菜单
Initialize or inspect a Hypo-Workflow workspace using the manifest-based format. Use for /hw:init when starting a repository, adopting an existing codebase, or checking whether legacy state can be adopted safely.
用 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.
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 | init |
| description | Initialize or inspect a Hypo-Workflow workspace using the manifest-based format. Use for /hw:init when starting a repository, adopting an existing codebase, or checking whether legacy state can be adopted safely. |
用户可见内容遵循项目 output.language；缺失时跟随当前对话语言。Schema key、配置 key、命令和路径保持英文。
Init creates a recoverable bootstrap context, not a Goal or Cycle. Init has no user-global configuration or setup prerequisite.
Import initializeWorkspace from this installed bundle's core/src/index.js and pass the target project separately as root. Every mutation uses a unique safe final { id } transaction option.
Use:
initializeWorkspace(root, { intent?, project_id?, workspace_id? }, { id?, faultInjector? })
The ordinary form is /hw:init <intended outcome>. Treat trailing text as the intended project outcome.
When no non-empty outcome is supplied, return the single init_outcome question and ask what the project should achieve. This branch is read-only. After the answer, summarize the understood outcome; that answer authorizes Init only, not a Goal, Cycle, or implementation.
| Classification | Behavior |
|---|---|
empty | Initialize the manifest format transactionally from the supplied outcome. |
unmanaged_brownfield | Read bounded safe repository evidence, create an Adoption Brief, then initialize transactionally. |
current | Report already_initialized and make no write. |
mixed_current_with_legacy_residue | Report residue without rewriting either model. |
legacy | Run inspectLegacyWorkspace read-only; migration is a separate future action. |
damaged_current | Fail closed with concrete repair evidence. Never call a legacy writer. |
A manifest-last transaction creates:
.pipeline/manifest.yaml with runtime, memory, and snapshot zonesruntime/active.yaml pointer to a bootstrap_jobproject_intent and adoption_brief Markdown Recordsinitial_snapshot is null. Init does not fabricate a Goal, Cycle, Receipt, Journal event, Recovery Pack, accepted Snapshot, platform adapter, generic Rules store, or global configuration.
For brownfield adoption, every fact records basis, confidence, and an existing repository-relative locator. Inference is never labeled confirmed. Preserve source bytes and mtimes.
Reject traversal, symlink evidence, secret-like values, raw credentials, and hidden reasoning before persistence. Errors must not echo rejected secrets. Preserve all repository files outside the staged .pipeline write set.
Explain the workspace classification, project/workspace identity, bootstrap reference, Adoption Brief facts and confidence, and the next useful public route in chat. For legacy or damaged workspaces, explain why no write occurred and what evidence or repair is needed.