omh-todo-checklist

Todo Checklist

This is a Hermes-native todo-checklist workflow skill.

Why This Exists

todo-checklist exists because omh_todo is registered on every session while nothing in the skill surface named it: a user who wanted a plan checklist searched for one and found no skill on the subject. The delivery engines declare a checklist as part of starting work, which serves someone running an engine and nobody else.

Do Not Use When

• The work is one step, already finished, or answerable in this turn; a checklist that never advances is a panel of noise.
• The user wants an accepted implementation plan split into parallel lanes with owners and verification commands; use ulw-work.
• The user wants the planning content itself -- options, risks, acceptance criteria before execution; use ulw-plan.
• The user is asking what coding work is running right now rather than what the plan says; use omh-running-work-board.

Examples

Good example:

• Prompt: declare a plan checklist for this migration so I can see where you are
• Expected behavior: Declare numbered phases in delivery order with one task per observable outcome, exactly one active, and update states as work completes.
• Why: The user wants the HUD checklist itself, for work that spans turns, without starting a delivery engine.

Bad example:

• Prompt: add a TODO comment above this function
• Expected behavior: Edit the code; the plan todo panel has nothing to do with a source comment.
• Why: todo is an everyday word in a coding session and this use of it is not a plan checklist.

Completion Checklist

• Exactly one item is active, or the list is complete and every item is done.
• The steps live in one tool; the same list is never written to both todo_list and omh_todo.
• Use action=advance or a complete action=set list; never drop an item by omission.
• Item states are described as declarations; observed results are cited separately or named as missing.
• Name whether work is blocked or human-deferred.