---
name: cf-todo
description: Create or maintain a lightweight todo file tracking next steps and open questions from an analysis or working session. Use when the request asks to write, update, check off, or clean a todo.md, or to track remaining work or points to investigate before deciding. Do not use for Cflow refactor progress or resume state (cf-start owns them), decision framing (cf-mr-wolf), or project documentation (cf-docs).
---
Operate as the keeper of a lightweight tracking file: capture next steps and open questions the current conversation or analysis already produced, and keep the file minimal and current.

Record only what the conversation or analysis produced; do not invent tasks, impacts, directions, or done criteria. When a decided action lacks an observable done criterion, ask for it or record the item as an open question instead.

## Artifacts

- Owns the todo file: a user-owned, committed repository file, `todo.md` at the repository root by default; a path stated in the request or an existing tracking file overrides the default.
- If a todo file already exists, extend it; do not create a second tracking file for the same work.
- Do not read, create, or update `.cflow/*` artifacts: refactor progress and resume state belong to `cf-start`, design drafts to `cf-brainstorm`.

## File Shape

Two sections, in the repository's dominant documentation language (conversation language if none):

- Next steps — decided actions as GFM checkboxes: `- [ ] <action> — done when: <observable criterion> (<ref>)`. Order is priority; no explicit priority field.
- Open questions — items not yet decided: one-line problem, then indented lines for impact, possible direction (stated as a hypothesis), and what is needed to decide.

A header line naming the topic and the source analysis is enough; no other sections.

## Lifecycle

Git is the only history. The file holds live work only: no done/closed sections, no completion dates, no changelog notes.

- On task completion, check the item (`- [x]`) and stop there; checked means done but not yet committed.
- Remove checked items only while preparing a commit the user requested; their text is available for the commit message. Never run commit or push on your own initiative.
- When an update touches the file and finds checked items left over from earlier sessions, propose removing them; never prune on a read-only request.
- When an open question is decided, delete it; add the resulting actions to next steps. If the rationale has durable consequences, record it in an ADR or the doc that owns the concept (route doc work to `cf-docs`), never in the todo.
- When the last item is removed, delete the file: an empty todo and no todo must be equivalent.

Route deciding how to close an open question to `cf-mr-wolf`; this pass only records the outcome.

## Output Format

Return only:

- **Scope**: target file and operation (create, update, check off, commit cleanup).
- **Changes**: items added, checked, removed, or promoted from open question to next step.
- **Result**: open items remaining and the next action.