kanbanr 0.1.0 — first public release

Released 1 October 2026.

kanbanr is a system of record for development done with Claude Code: the plan, the reasoning and the evidence live on a git-backed kanban board beside your code, and Claude keeps them current as part of doing the work. This is the first release anyone outside the project can install. It carries everything the project was built with, because kanbanr has been developed on its own board from the start — the board is public.

Highlights

• One binary, installed in one line. The CLI, the live monitor and the Claude Code skill are one executable, checked against the release’s SHA256SUMS by the installer. The installer puts the matching skill in place when Claude Code is installed.
• A board Claude recovers from. Every session starts from the board; a stop hook reminds Claude to record what changed. Nothing about the plan lives only in a transcript.
• Work that says why it exists. Each item carries a definition — a statement, the goals it serves, the six Zachman questions, EARS requirements each naming the test that proves it — and is approved before work starts. Change the definition and the approval lapses.
• Your process, as configuration. Kanban, Scrum, agile, TOGAF, PDCA, a design-control flow or your own file: each stage declares what an item needs to enter it and who signs off.
• Code traced to its reason. Commits carry Refs: kanbanr:FEAT-…; kanbanr why <file>:<line> walks from a line of code to its requirement and goal.
• Set up by interview. Say “set up kanbanr for this project” and Claude interviews you in plan mode — where the board lives, who you are, a charter drafted from your repository, the process — and sets it all up when you approve the plan.

What’s new

• The method: a project charter with goals; feature definitions; approval, ratification and named sign-offs; EARS and ISO/IEC 25010 checks; tests carried through planned → red → green; defects with their origin; retrospectives per milestone; lessons with confidence that decays.
• Processes: declarable gates per status (block or warn), presets as data, kanbanr check saying what the next stage needs, --override with the reason kept.
• Cadence, when you want it: sprints with a burndown derived from what actually moved, story points, releases planned up front and cut with notes.
• Traceability: one item, one branch; commit hooks that refuse unreferenced commits; trace and why; architecture decisions as documents joined to the items they affect.
• The monitor: board, item pages, review queue, sprints and releases, Gantt, workflow, charter and lessons, docs with Mermaid diagrams, a portfolio across projects, light and dark themes — updating live, read-only unless you start it to take verdicts.
• Sharing: a board is its own git repository; push it to a remote to share it. The push policy is a board setting (kanbanr remote push-policy).
• Also: a container image of the monitor, a GitHub issue mirror, import from existing task trackers, session summaries, a VS Code extension (in the repository).

Known limits

• The VS Code extension is not published yet; build it from editor/vscode/.
• The container image’s kanbanr --version says unknown and its binary carries no skill — fixed in 0.1.1.
• Only the Linux installer is verified by the release; macOS and Windows are built and tested in CI but their installers are not yet run end to end.

Installing

curl -fsSL https://github.com/startr-trade/kanbanr/releases/download/v0.1.0/install.sh | sh -s -- --version v0.1.0

See Installation. The complete list of changes is in the changelog.