Tracking Tasks
Vault
~/ghq/github.com/h3y6e/log — if missing, ghq get log.
Task Note
Path: task/YYYY-MM-DD-<slug>.md. Frontmatter: title, status (backlog→todo→in-progress→done/canceled). Sections: Goal, DoD (checklist), Research, Notes.
- Infer slug and title from context — don't ask.
- On session start: search with
anna recall "<text>", then read the matching file directly.
- Fill Goal and DoD before substantial work, then set status to
in-progress.
- The note is the source of truth. Sync after initial plan, each work batch, direction changes, and before final response.
- Evidence before claims — don't mark done until verification is recorded.
Graph
Make the Obsidian graph useful with [[wikilinks]]; do not treat notes as isolated logs.
- Link concrete context: active project/repo, related task notes, daily notes, issues/PRs, and ADRs/specs.
- When resuming a task, inspect linked notes/backlinks before broad search; prefer existing pages over new abstract concept nodes.
- When logging a cross-cutting finding in the daily note, link the active task and relevant project/source pages there too.
Daily Note
Triggers are session-wide — even without a task note, even on single-response tasks. Write at the moment of discovery, not batched at the end.
Path: obsidian daily → daily/YYYY-MM-DD.md. If CLI fails, use ~/ghq/github.com/h3y6e/log/daily/YYYY-MM-DD.md.
Triggers — TIL, workarounds, cross-cutting decisions, env/tooling issues, useful links, recurring patterns.
If a finding is both task-relevant and cross-cutting, log task impact in the task note and the broader concern in the daily note separately.
Obsidian CLI
The CLI is unstable. If any command errors, immediately fall back to direct file editing — do not retry or debug. Prefer direct editing over obsidian append for backticks or shell-sensitive content.
Workflow
obsidian daily → get today's date (use this, not date command)- Search for existing task with
anna recall "<query>"; if none, obsidian create path="task/YYYY-MM-DD-slug.md" template=task
- Edit directly — Goal, DoD, Research, Notes
- Add/update
[[wikilinks]] so graph/backlinks connect the task to related work
obsidian property:set path="task/..." name=status value=in-progress- After each batch, update Notes with findings/decisions/verification
obsidian task ref=<path:line> toggle- Final sync checkpoint
obsidian property:set path="task/..." name=status value=done
1---2name: tracking-tasks3description: Tracks task state and findings as Obsidian task/daily notes so work survives across sessions. Use when starting any multi-step task, resuming or continuing prior work (including phrases like "continue", "last time", "where were we", or a reference to an earlier task/issue/PR), switching direction or scope mid-task, wrapping up or reporting task status, or hitting a TIL, workaround, env/tooling quirk, or cross-cutting decision worth recording — even in a single-response task with no task note yet.4license: MIT5---67# Tracking Tasks89## Vault1011`~/ghq/github.com/h3y6e/log` — if missing, `ghq get log`.1213## Task Note1415Path: `task/YYYY-MM-DD-<slug>.md`. Frontmatter: `title`, `status` (`backlog`→`todo`→`in-progress`→`done`/`canceled`). Sections: Goal, DoD (checklist), Research, Notes.1617- Infer slug and title from context — don't ask.18- On session start: search with `anna recall "<text>"`, then read the matching file directly.19- Fill Goal and DoD before substantial work, then set status to `in-progress`.20- The note is the source of truth. Sync after initial plan, each work batch, direction changes, and before final response.21- Evidence before claims — don't mark done until verification is recorded.2223## Graph2425Make the Obsidian graph useful with `[[wikilinks]]`; do not treat notes as isolated logs.2627- Link concrete context: active project/repo, related task notes, daily notes, issues/PRs, and ADRs/specs.28- When resuming a task, inspect linked notes/backlinks before broad search; prefer existing pages over new abstract concept nodes.29- When logging a cross-cutting finding in the daily note, link the active task and relevant project/source pages there too.3031## Daily Note3233Triggers are **session-wide** — even without a task note, even on single-response tasks. Write at the moment of discovery, not batched at the end.3435Path: `obsidian daily` → `daily/YYYY-MM-DD.md`. If CLI fails, use `~/ghq/github.com/h3y6e/log/daily/YYYY-MM-DD.md`.3637**Triggers** — TIL, workarounds, cross-cutting decisions, env/tooling issues, useful links, recurring patterns.3839If a finding is both task-relevant and cross-cutting, log task impact in the task note and the broader concern in the daily note separately.4041## Obsidian CLI4243The CLI is unstable. If any command errors, **immediately fall back to direct file editing** — do not retry or debug. Prefer direct editing over `obsidian append` for backticks or shell-sensitive content.4445## Workflow46471. `obsidian daily` → get today's date (use this, not `date` command)482. Search for existing task with `anna recall "<query>"`; if none, `obsidian create path="task/YYYY-MM-DD-slug.md" template=task`493. Edit directly — Goal, DoD, Research, Notes504. Add/update `[[wikilinks]]` so graph/backlinks connect the task to related work515. `obsidian property:set path="task/..." name=status value=in-progress`526. After each batch, update Notes with findings/decisions/verification537. `obsidian task ref=<path:line> toggle`548. Final sync checkpoint559. `obsidian property:set path="task/..." name=status value=done`
h3y6e