with one click
hm-dream
Run the harness-mem dream daily action when the user invokes hm-dream.
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.
Menu
Run the harness-mem dream daily action when the user invokes hm-dream.
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
Run the harness-mem distill daily action when the user invokes hm-distill.
Run the harness-mem distill daily action when the user invokes hm-distill.
Evidence answerer for harness-mem memory admission and review. Use when grill-before-distill or review needs concrete support from packet evidence, observations, memory search, files, docs, tests, config, or command output. Does not write candidates or confirmed truth.
Architecture, product-boundary, roadmap, and long-lived-rule consultation for harness-mem memory admission and review. Use when a candidate's truth depends on design judgment rather than only evidence lookup. Does not write memory.
Standard memory admission mode for harness-mem (grill-me role). Runs automatically on distill — depth scales by risk, not a forced heavy loop every time. Three modes: deep interrogation, light checklist, lookback for stale truth. No writes. More than a review-stage helper: admission plus lookback.
Conversation autopilot for harness-mem. Use proactively when starting or resuming a task, when the user asks about previous decisions, when the user asks to remember a rule, when recent work becomes stable enough to preserve, or when a memory conflict appears.
| name | hm-dream |
| description | Run the harness-mem dream daily action when the user invokes hm-dream. |
This is a user-invocable harness-mem Daily command. Follow the action below through the configured harness-mem MCP server; do not replace it with terminal maintenance commands.
通过 MCP 查看 v3.1 DreamRun 账本,或在用户明确要求时触发一次 opt-in dream 维护。
Input: 可指定项目名($hm-dream bazi-apps)。省略则用 active project。
Default UX
默认 $hm-dream 是只读账本视图:展示最近一次 DreamRun 做了什么、为什么、是否失败、如何撤销。不要把 flags 或底层 CLI 参数作为用户主体验。
用户追问时用自然语言 drilldown:
看第 2 条为什么这么处理
撤销第 2 条
展开上一场梦
只看失败项
现在跑一次 dream
Steps
确认项目
get_project_status(project_root=<当前工作区>, host_client="codex") 读取 active project,并幂等检查项目 Hook默认读取最近账本
dream_ledger:
project_name=<project>展示摘要
applied / rejected / archived / failed 分组pending_review;v3.1 dream item 必须进入终态自然语言 drilldown
DreamRun,解释该 item 的 evidence、risk、proposed action、final action、reasonfinal_action=faileddream_ledger 读取指定 run_id 或最近账本用户明确要求跑一次
dream_run:
project_name=<project>用户明确要求自动 tick
dream_auto_tickdream.auto.enabled=false、没有活动、未到间隔而跳过撤销
undo_dream_item:
project_name=<project>run_id=<current-run-id>item_id=<dream-item-id>Notes
$hm-dream 不制造人工 review 队列;高风险 dream 结果按 policy 自动 reject/archive/fail。$hm-dream、自然语言和 Agent 背后的 MCP。