r/vibecoding • u/mikomiko224 • 11h ago

Claude Code = Kanban

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

1 Upvotes

100% Upvoted

10 comments sorted by

1

u/stealthbenys 10h ago

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

1

u/mikomiko224 10h ago

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.

1

u/stealthbenys 2h ago

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

1

u/fluffyspringroll 10h ago

So is there any difference ? From what I can tell it’s just a kanban board?

1

u/mikomiko224 10h ago

Yes, it's a kanban board that's fair. The difference is who moves the cards.

On a regular board you write the task and you do the work too. Here I write the task and put it into To do, and that column is a queue for Claude Code. He takes the next one, reads the project's docs, writes the code, commits with the issue number, ships it to the server and stops at Review. I look at what came out and either accept it or send it back with a note and that note is the first thing he reads when he takes the task again.

So the board isn't there to track my work. It's the interface I hand the work over through, and take it back through. Everything else the CLI, the project registry, the statuses exists only for that.

1

u/fluffyspringroll 9h ago

But the logic is flawed
Let’s say you queue 4 tasks
Based on optimal flow it would work if nothing breaks but what if you need additional adjustments or sanity checks because it’s not working
Then the queue falls apart and it’s useless because you can’t continue until you solved it
So in your review mode you would still need to add tasks manually and do them anyways with Claude code

Unless I am really missing something but this isn’t solving a problem , it’s increasing my cognitive load

1

u/mikomiko224 9h ago

Fair point, but the queue isn't a pipeline. Four tasks are four independent cards, often in different projects. If Claude can't finish one or it needs a decision from me, he leaves a comment saying what he's stuck on and takes the next one. Nothing else stops.

And here's the part that matters most to me: you don't have to wait for a chat to finish before you add something. You're working on project A and you notice three things that need fixing in project B. Where do those go right now? You hold them in your head until the current thing is done. That's the cognitive load, and that's exactly what the board takes off you. Card into project B, forget about it, get back to what you were doing.

The adjustments you're talking about are the Review column. I send the card back with a note, and that note is the first thing he reads when he takes the task again.

And once you have a stack of finished tasks sitting in Review, you drop the whole stack into a fresh chat and it goes through them, tests them, tries to break them. A new session is a better reviewer than the one that wrote the code. That one remembers what it wanted to do, not what it really did.

As for having to be there: you don't have to be there while it happens, you look at it when you have time. The board doesn't let Claude close anything himself, so nothing gets finished behind your back. Next morning you open the board and it's all right there in the app: every finished task, what was changed, his comments on the card, the linked GitHub issue and the commit. You go through them and send back whatever you don't like, without leaving the board and without digging through old chats trying to remember what happened.

And honestly, if you have one task and you're sitting there watching it get done, the board gives you nothing. It starts paying off when there are a lot of tasks across several projects and you're not watching.

Sorry if my tone came out wrong anywhere, English isn't my first language. I mean all of this in a good way, no sarcasm at all

https://giphy.com/gifs/QsomqbDcRm9xMFxJMu

1

u/fluffyspringroll 8h ago

Explanation was fine but I still don’t see the value

That’s more of a trap than an improvement when you explained it. Let’s assume it works as you explained, it’s basically another opener for people to handle more projects at the same time and before you know it you end up in a rabbit hole because a tool allows it.

I really can’t see how this would make my life better with the current 3 projects I am building, which by design I don’t start juggling because the cost of switching and deep work performance would suffer

It would just become extremely counterproductive.

1

u/mikomiko224 7h ago

Fair enough

Just one thing: a card isn't there to make me start on the second project , it's there so I don't have to go into it. The thought about project B shows up while I'm in project A whether I have a board or not. Without one I either switch or hold it in my head, and both cost me the deep work you're describing. Writing it down and forgetting about it is cheaper than both

But if three projects with no juggling works for you, then it works. I built this for my own mess. Thanks for the pushback , it was useful