菜单
Persist focused day-to-day project facts without opening a Goal or Cycle. Use for /hw:maintain and for ambient capture of requirements, preferences, decisions, or feedback in a current workspace.
用 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 | maintain |
| description | Persist focused day-to-day project facts without opening a Goal or Cycle. Use for /hw:maintain and for ambient capture of requirements, preferences, decisions, or feedback in a current workspace. |
Maintain records project facts; it does not create an ordered Delivery.
用户可见内容遵循项目 output.language；缺失时跟随当前对话语言。Schema key、配置 key、命令和路径保持英文。
For /hw:maintain:
requirement, preference, decision, or feedback.RecordPatch with a stable dedupe key and explicit source references.commitRecordPatch and refresh .pipeline/memory/index.yaml plus INDEX.md.If the request has a bounded deliverable and final acceptance, route to Goal. If it has ordered dependent stages, route to Cycle.
The Official Codex UserPromptSubmit Hook may extract a clean durable semantic delta. createAmbientMaintainStore first appends a Recovery Journal event and stages a proposal under .pipeline/memory/inbox/. A staged Inbox item is not Record authority.
Only the main Agent may validate and promote the exact staged RecordPatch. A recorder Subagent may propose a patch, but cannot commit authority. Promotion verifies the proposal binding, writes the Markdown Record, and refreshes derived indexes. Duplicate semantic facts are deduplicated; changed facts require explicit supersedes.
PostToolUse records bounded evidence and emits only relevant, deduplicated documentation or Record reminders. It does not force a write after every tool call.
Never persist raw passwords, tokens, credentials, hidden reasoning, or full transcripts. secret_refs may point to separately authorized secret locations, but secret values are not Workflow authority.
Write only through the current manifest-selected memory and recovery APIs. Never update legacy state.yaml, cycle.yaml, log.yaml, PROGRESS.md, rules.yaml, or knowledge/.