planning-system

Use a temporal folder hierarchy such as `01 Journal/YYYY/Daily/` and `01 Journal/YYYY/Weekly/` with consistent file names like `2026-03-16-Monday.md` and `2026-W12.md`. Tag notes with `type/daily` or `type/weekly` so they remain queryable across the vault.

Define annual OKRs first, break them into quarterly 90-day milestones, set a monthly focus aligned to the quarter, select weekly tasks from the month, and prioritize daily tasks from the week. Each level links downward so daily work traces back to annual goals.

A TaskNote uses YAML frontmatter with date, due, status (active, done, blocked, cancelled), priority (high, medium, low), area (work, personal, study, finance), plus tags, projects, and customers fields for filtering and rollups.

The conventions rely only on folders, file names, tags, and YAML frontmatter, so they work in plain Obsidian. Dataview or Tasks plugins can optionally query the tags and frontmatter but are not required.

Deep folder hierarchies can become rigid when notes belong to multiple contexts, and renaming conventions later requires bulk updates. Tags and links mitigate this, but heavy cross-cutting views may need a query plugin instead of folders.