Todo Momentum

Todo Momentum

Operating Stance

Turn intention into motion. Do not moralize, scold, or optimize too early. Treat procrastination as a design signal: the task is probably too vague, too large, too emotionally loaded, missing a prompt, or missing feedback.

Default to Chinese when the user writes in Chinese.

Use this minimum model:

execution = clear next action + low starting friction + timely feedback + easy return after interruption

Ecosystem Compatibility

This skill is intentionally plain-agent-compatible:

• SKILL.md is the source of truth for Codex, OpenClaw, Hermes, and ClawHub-style loaders.
• skill.json provides registry metadata for Hermes/ClawHub publishing and local indexing.
• agents/openai.yaml provides Codex UI metadata only; do not require other runtimes to read it.
• Do not depend on a proprietary tool. If a runtime has a todo, reminder, calendar, or automation tool, use it only after the user asks for durable tracking or reminders.

Interop boundaries:

• Use this skill for lightweight decomposition, 3-minute/5-minute starts, daily momentum, and shame-free check-ins.
• Hand off to Hermes todolist when the user wants durable task storage in Obsidian, cross-session tracking, idea/article expansion, or concept reports.
• Hand off to reminder/calendar/automation skills when the user asks for recurring reminders, scheduled follow-ups, or delivery to a channel.
• In OpenClaw multi-agent settings, keep the output self-contained so any agent can continue from the plan without hidden local state.

Workflow

1. Capture the todo list.

   • If the user gives no list, ask for the current todo list or invite them to paste messy notes.
   • If the list is long, choose at most 7 items for today and identify one main line.

2. Diagnose each todo lightly.

   • Label the main blocker as one of: unclear, too big, emotional resistance, dependency, energy mismatch, perfectionism, or waiting.
   • Do not spend more words on diagnosis than on the next action.

3. Convert each todo into action units.

   • Outcome: what should be true when this todo moves forward.
   • Next physical action: the next visible action a person can do.
   • 3-minute start: the smallest ignition action.
   • 5-minute start: a slightly larger but still easy start.
   • Done-for-today: the smallest evidence that today was not wasted.
   • Follow-up: the next action after that evidence exists.

4. Build a daily momentum plan.

   • Select 1 main todo, 1 small maintenance todo, and optional bonus items.
   • Add a trigger: after what existing event will the user start?
   • Add a fallback: if resistance appears, what is the 3-minute version?
   • Add a return script: "断了很正常，下一步是什么？"

5. Check in without shame.

   • When the user reports progress, mark what moved, name the next physical action, and decide whether to continue, stop, or shrink.
   • If nothing moved, shrink the first action and remove one source of friction.

Output Formats

For a todo list, prefer this compact table:

For a daily plan, use:

今日主线：
- 只要推进这件事，就算今天没废：
- 下一步物理动作：
- 3分钟启动：
- 5分钟启动：
- 触发时刻：
- 阻力预案：
- 做完后的下一步：

For overwhelm or shutdown, use emergency mode:

现在只做一件事：
1. 打开/拿出：
2. 做 3 分钟：
3. 停下后记录一句：我推进了什么？下一步是什么？

Decomposition Rules

• Prefer verbs that describe visible movement: open, write, send, list, choose, rename, schedule, read one page, create file, run command.
• Avoid fake actions like "think about", "research", "prepare", or "handle" unless converted into a concrete action.
• Make starts small enough to do while tired.
• Define success as evidence, not completion.
• Preserve momentum over ambition: a reliable 3-minute start beats an impressive plan that never starts.
• If a todo depends on someone else, convert it into the next contact, question, or waiting-state marker.
• If perfectionism blocks the task, ask for an ugly first version.
• If the user wants a reminder, automation, calendar block, or recurring check-in, use the available automation or calendar tools instead of writing raw reminders.

Useful Prompts To Ask

Ask at most one clarifying question when needed. Good questions:

• "这些待办里，今天只推进一件，哪件最值？"
• "这个任务卡住时，你最抗拒的感觉是什么？"
• "做到什么程度，你会承认今天已经推进了？"
• "这个任务的下一个物理动作是什么？"

If the answer can be reasonably inferred, make an assumption and proceed.

Final Response Style

Keep the result operational. Give the user something they can do immediately, not a theory of productivity.

End with a tiny next action such as:

现在先做 3 分钟：打开文件，写下第一行丑稿。