obsidian-kanban

Create Kanban boards as markdown files in a project-local kanbanboards folder using H2 lane headings and TAB-indented card bodies. This enforces kanban-plugin frontmatter and a trailing settings block so boards render correctly in Obsidian and remain readable in any editor.

Track implementation tasks and preserve persistent context across Claude sessions by creating a companion _context.md file alongside each board. This maintains feature memory within the repository project without relying on external services.

Manage detailed issue specs by creating per-board linked issue folders containing full implementation specifications. Each card links to its corresponding issue file, keeping the board compact while preserving detailed tracking information.

Obsidian Kanban formatting remains fully readable in any text editor because boards are plain markdown files. The enforced kanban-plugin frontmatter, H2 lanes, and TAB-indented cards ensure correct rendering in Obsidian while maintaining universal plain-text compatibility.

Bootstrap a self-contained kanbanboards Obsidian vault directly in a project to gain example boards, plugin-friendly config, and reference guides. This provides a reproducible, repository-local workflow for tracking tasks and linking detailed issue specs.

Kanban boards fail to render when missing required kanban-plugin frontmatter, H2 lane headings, TAB-indented multi-line card bodies, or the trailing kanban:settings block. Enforcing these formatting rules ensures boards display correctly in the Obsidian kanban plugin.