kanbanlisted

# Kanban A local, file-based task system designed for vibe coding: the LLM is the primary user of the board, not the human. The board's main purpose is to keep context alive between sessions — what's done, what's next, *why* past decisions were made, and *how* we verify each task is genuinely complete. ## Concept Three nested levels, encoded directly in the filesystem: ``` .tasks/ ├── M1-auth/ # milestone (kebab-case, M<N>- prefix) │ ├── PRD.md # milestone product brief + acceptance scenarios │ ├── oauth/ # epic │ │ ├── doc.md # epic brief (objective, constraints, acceptance criteria) │ │ ├── TASK-001.md # task │ │ └── TASK-002.md │ └── session/ │ ├── doc.md │ └── TASK-003.md └── M2-billing/ ├── PRD.md └── ... ``` Each task file has YAML front matter (id, status, milestone, epic, branch, priority, blocked_by, type, title, description) and a Markdown body with **three** sections: - **`## Actions`** — checkboxes describing concrete coding actions: `[ ]` open, `[x]` done, `[!]` blocked - **`## Definition of Done`** — checkboxes describing **verifiable** acceptance criteria (tests passing, wired integrations, end-to-end scenarios). All must be `[x]` before the task can close. - **`## Discussion`** — append-only log of design decisions, dated Task IDs are global (`TASK-001`, `TASK-002`, ...) so files can be moved between epics without renumbering. The folder path