tasks

name	tasks
description	Markdown-based task system. Write tasks as checkboxes, tell Claude "do my tasks", and review results. Triggers on "set up tasks", "create a task", "do my tasks", "do today's tasks", "work on my X task", or "read my feedback".

Tasks

Path convention: All paths below use <vault-root> to mean the Obsidian vault's root directory (the working directory where Claude Code is launched). For example, <vault-root>/daily/2026/03/tasks/2026-03-15.md is daily/2026/03/tasks/2026-03-15.md relative to the vault root. Do not prepend / or use an absolute filesystem path — always resolve relative to the vault root.

Routing

• "set up tasks" → Set up the task system:
  1. Create tasks/ folder with README.md and overview.md (copy from assets/)
  2. Ask the user if they want to install the Tasks community plugin (obsidian-tasks-plugin). If yes: point the user to this link to install it.
  3. Show available commands
• "create a task" → Create tasks/<slug>.md with - [ ] items pre-filled from user description, and add a log link at the top of the tasks file: Log: [[daily/YYYY/MM/tasks/YYYY-MM-DD]].
• "do my tasks" → Execute Tasks (see below)
• "do today's tasks" → Do Today's Tasks (see below)
• "work on my X task" → Search daily notes for matching task, create a task file, then Execute.
• "read my feedback" → Read latest log in <vault-root>/daily/YYYY/MM/tasks/, find ## Feedback, act on it.

---

Execute Tasks

1. Read all .md files in tasks/ (skip README.md and overview.md)
2. Skip done tasks — done = no unchecked items (- [ ] or - [/]). If nothing to do, say so and stop.
3. For each unchecked item: a. Mark in progress: - [ ] → - [/] b. Do the work. Follow any rules in the task file. c. Mark done: - [/] → - [x] task ✅ YYYY-MM-DD d. Append to log at <vault-root>/daily/YYYY/MM/tasks/YYYY-MM-DD.md with what was done
4. After all items, add a log link at the top of the tasks file: Log: [[daily/YYYY/MM/tasks/YYYY-MM-DD]]
5. Cleanup — if no unchecked items (- [ ] or - [/]) remain in the task file, remove completed items, keep the log link(s) at the top, and, if the file is now empty, add one empty checkbox with a space after (- [ ] ) so the user can easily start the next task. The log at daily/YYYY/MM/tasks/YYYY-MM-DD.md is the permanent record.

Log format

# Log — YYYY-MM-DD

## Task Prompts
[copy of task file contents — preserve done markers and dates, e.g. `- [x] task ✅ YYYY-MM-DD`]

## Progress Log
- What was done
- Key decisions

---

Do Today's Tasks

1. Read today's daily note at <vault-root>/daily/YYYY/MM/YYYY-MM-DD.md
2. Find checkbox items (- [ ]) in the note (e.g. under a ## Tasks section)
3. Copy them into a new task file at tasks/YYYY-MM-DD-tasks.md
4. Show the user what was found and ask to confirm before executing
5. If confirmed, Execute Tasks on that file (follow the Execute Tasks workflow above)

---

Rules

• Never push code unless explicitly asked
• Follow constraints in the task file
• Task files: any .md in tasks/ except README.md and overview.md
• Log files: <vault-root>/daily/YYYY/MM/tasks/YYYY-MM-DD.md
• Output files: any files generated by a task (docs, reports, summaries, etc.) go in tasks/output/