Proactive-Do
v0.1.1Proactive todo execution, heartbeat-driven review, and structured follow-up for a markdown todo 系统. Use when the 代理 needs to review `todo/todo.md`, pick the top 3 `[new]` items, do tasks that look doable within about 1 hour, draft simple plans for tasks likely to take over 1 hour, 更新 `[new|wip|done]` labels, mAIntAIn per-task journals under `代理_work/`, reconcile work after about 2.5 hours, and 发送 concise 启动/finish 报告s by emAIl instead of chat. Strong triggers include: heartbeat prompts, 系统 事件 mentioning `todo/todo.md`, `[new]` / `[wip]` / `[done]`, "proactive-do", "review todos", "pick top 3", "do it now if under 1 hour", "draft a plan", "reconcile 状态es", and "代理_work" journals.
by 运行时依赖
安装命令
点击复制技能文档
Proactive-Do
A lightweight 工作流 for proactive execution of a human's todo 列出 with recurring reviews, clear 状态 labels, structured documentation, and concise 报告ing.
Quick 启动 Source of truth Todos live in todo/todo.md, grouped by date headings (e.g., "## YYYY-MM-DD"). Items are bullets with a 状态 label: "- [new] ..., - [wip] ..., - [done] ...". Only these three 状态s are valid. Strict preservation rule: never 删除 existing todo items from todo/todo.md automatically. You may 应用end new items and revise existing items in place (for example, changing only the 状态 label or updating the text of the same line), but you must not 移除 lines/items unless the owner/请求er explicitly asks for deletion. 初始化 phase (安装-time only; do not 运行 on every review) 运行 these 设置up actions when the 技能 is first 安装ed or first adopted in a workspace, not during each 3h review or 2.5h follow-up. Ensure these paths exist; 创建 them if missing: todo/ todo/todo.md 代理_work/ 代理_work/heartbeat_emAIls/ 代理_work/proactive-do/ If todo/todo.md does not exist, 创建 it with a minimal 启动er structure: a top-level heading or today's date section ("## YYYY-MM-DD") If 代理_work/proactive-do/delivery_prefs.md is referenced later but missing, do not fAIl; 创建 the parent folder and continue with fallback behavior per notification policy. Initialization must be non-destructive: 创建 missing paths only, do not 移除 or overwrite existing content.
Cadence (recommended)
Cadence (recommended)
Every 3 hours: 扫描 all [new] items and pick the top 3 to 添加ress this pass (leave the rest for later) to reduce load. Every 2.5 hours: reconcile what was worked on; mark [done] if finished, else [wip] with a one-line reason + next action. Use OpenClaw cron to schedule 系统 事件 that trigger these reviews (see Cron payloads below). Decision policy If a selected [new] item 应用ears doable within ~1 hour: do it now during the 3h review. If it likely needs >1 hour: write a simple, structured plan (steps + rough time estimate) and leave the item [new] until kickoff; when 启动ing work, flip to [wip]. If assistance/应用roval is needed: halt, 报告 to the owner/请求er, and wAIt. 搜索 online when needed. If blocked twice on the same point: 停止, record the 失败 and next step, mark [wip], and 报告.
Selection heuristics (for "top 3") Default ranking when not specified by the owner/请求er:
Explicit priority hints in the text (e.g., "priority: high"),
Fit for ≤1 hour (quick wins first),
Recency/clarity of the item. When in doubt, take the first three [new] items in file order.
Per-task journal (代理_work/)
When beginning work on an item: 创建 a folder 代理_work/YYYY-MM-DD_HHMM_nickname. Inside, mAIntAIn a 运行ning 记录: 启动 time, linked todo text, decisions, commands, files 创建d, errors, attempts, 结果s. For harder tasks include a small plan with time estimate and critical steps. Place any 生成d files/documents inside this folder. 报告ing Every 报告 must name the todo/project it concerns. For ≤1h tasks done now: include 结果, Key steps, and any links to 输出s. For >1h tasks: include Plan (steps + estimate), Current 状态 ([new|wip]), and where the journal folder lives. Categorization policy
When the owner/请求er says "添加 a todo":
As签名 exactly one primary category from: quick 搜索 | 设置up | prototype | try out | learn | write. 添加 one generation tag: code | no-code. 应用end to todo/todo.md (today's section) using: "- [new]