plandecklisted

A live visual Kanban board and continuity layer for long-running agentic tasks. Nobody wants to read a markdown plan or stare at raw HTML while an agent grinds for an hour, so Plandeck turns the plan into a board that organizes itself. Use it when a task is multi-step, long-running, or needs visual planning. Break the work into cards, declare which card depends on which, and Plandeck computes the critical path, auto-promotes cards to Ready as their dependencies clear, rolls up story-point estimates into an honest percent complete, and names the one next action. Plans, observed transitions, and last-known-good snapshots stay as plain files on disk, so they survive /clear and context resets. After a reset, run plandeck next to recover the single next move and its recent history. If the plan stops parsing, run plandeck doctor before using git. Renders a live board in the browser over SSE. Triggers on plan a project, break down a task, kanban board, task board, visual plan, long-running agent, agentic task, track
OthmanAdi/plandeck · ★ 63 · Web & Frontend · score 79

Install: claude install-skill OthmanAdi/plandeck

# Plandeck Plandeck keeps a plan on disk as `plan.yaml` and renders it as a live Kanban board that reorganizes itself as you edit. You author cards (id, estimate, dependencies, next action). Plandeck computes the rest: which cards are Ready, the critical path, progress rollups, and the single next move. It grows out of planning-with-files (crash-proof file plans plus a completion gate). What is new in Plandeck is the live visual board plus a deterministic intelligence layer over the yaml. It contains no AI and no LLM, only pure, tested functions. ## When to use it Reach for Plandeck when the work is multi-step and worth tracking: - A task that needs 5+ steps, spans a long session, or will outlive a `/clear`. - Work with real dependencies, where order matters and one card unblocks others. - Anything you want to see: a board with lanes, estimates, and a critical path. ## When not to use it Skip it for one-shot work: - A single edit, a quick answer, a two-step fix. - Anything you will finish before the next context reset. Do not build a board for work that does not need one. The overhead pays off only when the plan has to persist and coordinate. ## Files in a plan directory | file | role | |---|---| | `plan.yaml` | The single source of truth (the board). You read and write it; the board re-renders live. | | `archive.yaml` | Completed cards moved out of the live plan. Their ids still satisfy dependencies. | | `plan.md` | The charter a human or agent reads first: north s