name: weasleys-wizard-wheezes-obsidian-kanban description: Create, normalize, and reorganize Obsidian Kanban plugin markdown boards. Display name: Weasleys Wizard Wheezes - Obsidian Kanban. Use when working with Obsidian Kanban .md files, turning ledgers, review ledgers, tables, checklists, audit notes, or issue lists into board columns and cards, reformatting existing Kanban boards for readability, or preserving full content while making cards easier to scan. Trigger on requests like “把台账转成 Obsidian 看板”, “整理这个 Kanban 文件”, “优化看板格式但不要删内容”, or “把 Markdown 清单改成 Kanban”.

Weasleys Wizard Wheezes - Obsidian Kanban

Use this skill to edit Obsidian Kanban plugin markdown files directly and safely.

0. Quick examples

Example A: ledger → board

User request:

把《第一轮评论台账》整理成 Obsidian 看板，不要删内容。

Expected approach:

1. read the source ledger
2. identify the main organizing axis, usually status or priority
3. create columns
4. convert each row into one card
5. shorten only the card title
6. preserve the full details in nested bullets

Example B: messy board → cleaner board

User request:

这个 Kanban 太难看了，帮我整理一下，但别删信息。

Expected approach:

1. keep frontmatter and kanban settings
2. keep existing columns unless the user asks to change them
3. shorten card titles for scanability
4. move detail into nested bullets
5. add lightweight markers only if they improve readability

1. Core principle

1. Preserve plugin-recognized structure.
2. Prefer direct markdown editing over UI simulation.
3. Unless the user explicitly asks for compression, do not delete content.
4. Optimize for two layers at once:
   1. board-level scanability
   2. card-level information fidelity

2. Recognize a standard board

Treat the file as an Obsidian Kanban board when it contains both of these markers:

---
kanban-plugin: board
---

and/or a settings block like:

%% kanban:settings

Column headings are typically ## Column Name. Cards are typically markdown task items under each column.

3. Safe editing rules

1. Keep the frontmatter valid.
2. Keep the kanban-plugin: board marker intact.
3. Preserve the %% kanban:settings %% block unless the user explicitly asks to change board behavior.
4. Do not silently convert the board into a normal note.
5. Do not remove card details when the user asks only for formatting or reorganization.
6. When uncertain about advanced plugin-specific syntax, read the existing file first and make the smallest valid edit.

4. Default transformation strategy

When converting a structured source document into a Kanban board: