name: todolist-md-clawdbot description: Operate on todolist-md Markdown todo files. Read + summarize tasks, propose edits, and write outcomes back into Markdown using only <!-- bot: ... --> markers (line-stable write-back).

todolist-md-clawdbot

Operate on todolist-md: a Markdown-first todo viewer/editor. The app does not contain an AI; the bot reads/writes Markdown.

Operating rules (must follow)

1. Markdown is the system of record.

• It’s fine to discuss in chat, but final answers/decisions must be written into Markdown.

2. Use only bot markers of this form.

• <!-- bot: ... -->
• Do not introduce other syntaxes (no Question[id=...], no custom metadata blocks).

3. Preserve task identity.

• todolist-md derives task IDs from Markdown line positions.
• Some storage backends also have a stable identity key (e.g. Drive fileId, local path, S3 bucket+key).
• Do not “replace” a file in a way that changes its identity key unless the user explicitly accepts it.

4. Keep write-back edits line-stable.

• Avoid adding/removing lines inside an existing task item or its description blockquote.
• Prefer single-line, in-place edits (edit text on an existing line).

5. Last review stamp (Option B: top-of-file header line)

• Goal: a single line near the top recording last bot review time.
• Rule: never insert a new line once the header exists. Only update the existing header line.
• If the header does not exist, you may insert it at the very top only if the user explicitly opted into Option B.
• Canonical format:
  • <!-- bot: last_review --> 2026-02-04T15:39Z root=<rootFolderId> model=<model>

6. Never complete tasks without explicit user confirmation.

Markdown conventions (what todolist-md expects)

• Tasks use GFM checkboxes: - [ ] and - [x]
• Optional tags: #tag
• Optional due date: due:YYYY-MM-DD
• Optional description: a blockquote directly under the task

Storage Q/A (first run)

Ask once, then persist the answers (in memory/config) for future runs.

• Q: storageKind?
  • A: google-drive | local-folder | s3 | other
• Q: What is the stable identity key for files?
  • Drive: fileId
  • Local: path
  • S3: bucket+key
• Q: Where is the root?
  • Drive: rootFolderId
  • Local: root directory path
  • S3: bucket + optional prefix

Chrome app integration: enable/disable per-file

When a Drive folder contains many .md files, not all of them should necessarily be AI-reviewed.

Recommendation (simple + app-controlled):

• The Chrome app should write a small per-file config key/marker so the agent can know whether a file is opted-in.

Two easy options:

Option 1: a dedicated Drive config file (preferred)

Create a config file in the same folder:

• .todolist-md.config.json

Example:

{
  "ai": {
    "enabled": true,
    "include": ["*.md"],
    "exclude": ["todoapp.md"],
    "botSuggestedSectionTitle": "Tasks (bot-suggested)"
  }
}