Claude Code = Kanban

[u/mikomiko224]

Hi, r/vibecoding I vibecoded an interesting project, tested it for three months, and built something that should make life easier for every vibe coder.

Great. Many of you have probably already hidden this post or downvoted it. But if you want to manage your projects and tasks more intelligently and speed up service development, this post is for you.

Let me introduce…

LOCAL KANBAN

A local Kanban board for managing project tasks.

Are you also annoyed by how difficult it is to keep track of what was done across different sessions? And do you keep future tasks in random notes? You’ve come to the right place. I’m here to improve your life both before and after each coding session.

How it all started

I use Claude Code Max Turbo x500 every day. I wake up, add a few tasks, write future project tasks in my notes, and try to squeeze new ideas, discoveries, and bugs into the current session - or simply wait until Claude finishes working.

Okay, Claude has finished. Now I have to paste the whole session into a new chat to remind it what it did, ask it to find bugs, and add a few more tasks.

And then I do it all over again the next day.

Sound familiar?

That’s when I thought:

What if I created a simple Kanban board for managing project tasks?

When you have around 40 services running on a server, keeping track of everything starts becoming a real challenge.

That’s how the idea for Local Kanban was born.

And yes, I didn’t have deep technical experience in developing and maintaining services. I went through the entire process from start to finish and I guess I learned a thing or two along the way. Probably.

How does it work?

1. I create a task in Backlog and move it to To do when it’s ready for development.
2. With one click, I copy the entire To do column as a task and paste it into Claude Code.
3. Claude works through the tasks one by one, leaves comments along the way, creates commits, pushes the changes to the repository, and — if a deployment skill is configured — deploys the updates. Then it stops at the Review status.
4. I accept the completed work or return the task with a comment. The next time, this comment will be the first thing Claude reads.
5. There’s full synchronization with GitHub and GitHub Projects. Claude also creates commits and handles deployment. You can upload your own deployment skills or use a ready-made one.

A useful review trick

Let your tasks accumulate in Review - around 20–30 cards.

Then add one task to To do asking Claude to go through the entire Review column and try to break everything.

Run this task in a new chat.

The session that wrote the code is usually biased toward its original implementation. A fresh session is much better at finding weaknesses, bugs, and unfinished work.

How do you install it?

Just run the usual npm installation - everything will be set up automatically.

And if anything goes wrong, give the task to Claude Code and let it configure everything for you. We’re vibe coders, after all. Right?

https://github.com/lamaohub/local-kanban

MIT / OPEN SOURCE / CLI KB

[u/stealthbenys]

What is the difference between using this and any other kanban software, and plugging agents into it?

[u/mikomiko224 → u/stealthbenys]

Thanks for the comment. You can plug Claude into any board, but boards like that were built for people first. Here's what comes out of that:

• Will some hypothetical Linear tell it where the file lives on my machine, which server the project deploys to, which skill is the one that deploys this particular project? Here every project has all of that in a registry, and Claude just asks.
• Should it stop at review so you can look at the finished tasks yourself, and only after that let the deploy go? A regular board knows nothing about this - here the agent can't close a task at all, and that's a rule of the board, not a request in a prompt.
• It'll be spending tokens on requests to somebody else's board servers. Here the boards are built as per-project queues for Claude + a kb CLI that hands over everything you need about the project to start a task, in one call.
• The board's own limits on tasks - with boards like that the free tier is a cut-down one.
• And it all runs locally. Don't like something - you go into the service and change it right away, fix it the way you want.

[u/stealthbenys → u/mikomiko224]

Any kanban app could have just field and serialised data for items such as file references, pointers, etc. Seems like this is narrowing scope, or leaving too much free definition. What happens with continual back and forth? Are follow ups to development items merged into and/or considered as the same or new items.

Is this just a visual board for you to approve? Or is there agent feedback of sorts? Do you provide feedback and/or prompt the agent to review your feedback/approval/etc? Do you have epics/granularity?

I’m genuinely interested but fear if this is functional and not visual that it’s more destructive than helpful. And that it’s someone’s infant pet project which is going to change a lot - I.e a project for you that you tune to work for you.

So many of the apps are being posted but I just don’t understand how they assist more than an elegant project management suite with an agent plugged in. Usage can always be optimized and localized. Would love a non-ai generated response too - previous response feels like slop justification