obsidian-kanbanlisted

# Obsidian Kanban ## Overview Create and maintain Obsidian Kanban boards as durable task systems rather than one-off lists. Default to a mixed task model: capture simple work as lightweight cards, then upgrade complex work into linked notes when the task needs more context, history, or attachments. For GTD boards, prefer trusted list semantics over generic priority queues: the board should clarify what the task is, where it belongs, and what the next visible action is. ## Workflow 1. Identify the target board file and read the current structure before editing. 2. Preserve the existing board frontmatter, list names, archive separator, and `kanban:settings` block unless the user asks for structural changes. 3. Decide whether each task should remain a lightweight card or be upgraded to a linked note. 4. Apply the task conventions below consistently so future edits remain predictable. 5. Validate the board after editing: headings still align with lists, cards still sit under the intended list, indentation remains valid Markdown, and the settings block is still intact. ## Task Model ### Lightweight card Use a lightweight card when the task is actionable without extra documentation. Prefer this shape: ```markdown - [ ] Prepare quarterly planning draft @{2026-05-02} @@{09:00} #planning #work - [ ] Pull current metrics - [ ] Draft agenda ``` Use this model for fast capture, inbox triage, and routine task maintenance. Treat `priority` as optional rather than foundational.