mrlesk (u/mrlesk) - Readit News

mrlesk commented on Show HN: Vibe Kanban – Kanban board to manage your AI coding agents github.com/BloopAI/vibe-k... · Posted by u/louiskw

slig · 2 months ago

How does this compare with Backlog.md? [1]

[1]: https://news.ycombinator.com/item?id=44483530

mrlesk · 2 months ago

Hi. I’m the author of backlog.md . Your team did a great job on Vibe Kanban. It looks great and has a cool name. I like to see more tools trying to solve the human-ai agent interaction for building projects.

I wish you all the best with this tool!

mrlesk commented on Backlog.md – Markdown‑native Task Manager and Kanban visualizer for any Git repo github.com/MrLesk/Backlog... · Posted by u/mrlesk

adobbs · 2 months ago

Brilliant! Thank you for sharing.

Had similar success with making some more markdown files to help guide the agent but never would have thought of something this useful.

Will try your workflow and backlog on a build this week.

mrlesk · 2 months ago

Backlog.md is still a bit rough on the edges but is definitely a proof that markdown files and AI Agents work really well together. I started working on it exactly a month ago

mrlesk commented on Backlog.md – Markdown‑native Task Manager and Kanban visualizer for any Git repo github.com/MrLesk/Backlog... · Posted by u/mrlesk

TimMeade · 2 months ago

That's look fascinating. I will certainly be testing it in the morning! Thanks!

mrlesk · 2 months ago

Thanks. Let me know if you have any feedback

mrlesk commented on Backlog.md – Markdown‑native Task Manager and Kanban visualizer for any Git repo github.com/MrLesk/Backlog... · Posted by u/mrlesk

crashabr · 2 months ago

Really nice! Have you thought of interfacing with the todo.txt ecosystem?

mrlesk · 2 months ago

Didn’t know this tool. Thanks for sharing

mrlesk commented on Backlog.md – Markdown‑native Task Manager and Kanban visualizer for any Git repo github.com/MrLesk/Backlog... · Posted by u/mrlesk

nzach · 2 months ago

Is there a proper way to use this project without commiting files to git ? I just want to try it out in a project I'm working on, but don't want to put it in the history.

What I did is to add the backlog folder into the .gitignore file, but after every command I get a lengthy error about a git command error.

And even if I were to add these files to my repository, I would want to add them manually.

mrlesk · 2 months ago

I made it configurable and autoCommit is false by default

mrlesk commented on Backlog.md – Markdown‑native Task Manager and Kanban visualizer for any Git repo github.com/MrLesk/Backlog... · Posted by u/mrlesk

urlwolf · 2 months ago

How is this different from taskwarrior? I feel the use cases are overlapping (which is a good thing as taskwarrior rewrite in rust is a mess)

mrlesk · 2 months ago

Never heard of taskwarrior. I will check it out. Thanks for sharing

mrlesk commented on Backlog.md – Markdown‑native Task Manager and Kanban visualizer for any Git repo github.com/MrLesk/Backlog... · Posted by u/mrlesk

thelittleone · 2 months ago

I've had same experience. Taskmaster-ai was pretty good, but sometimes the agent ignored it as the project grew larger (can probably prevent that now using claude code hooks).

Trying this project today looks nice. I see you have sub-tasks. Any thoughts on a 'dependency' relation? I.e., don't do X if it is dependent on task A which is not complete.

FYI, there is a 404 in the AGENTS.md GEMINI.md etc pointing to a non existing README.md.

mrlesk · 2 months ago

Yep. Dependecies are supported via —dep parameter.

Will check the 404 issues. Thanks for reporting it

mrlesk commented on Backlog.md – Markdown‑native Task Manager and Kanban visualizer for any Git repo github.com/MrLesk/Backlog... · Posted by u/mrlesk

kurtis_reed · 2 months ago

Part of this confusing trend of naming projects like files

mrlesk · 2 months ago

It is so confusing that I had to add custom instructions for Codex telling him that Backlog.md is the project folder and not a file. He was wasting few mins trying to CAT Backlog.md instead of CD

mrlesk commented on Backlog.md – Markdown‑native Task Manager and Kanban visualizer for any Git repo github.com/MrLesk/Backlog... · Posted by u/mrlesk

tptacek · 2 months ago

This is a good idea. But the screenshots you have show lots of tasks in a project; how are you dispatching tasks (once planned) to an agent, and how are agents navigating the large number of markdown task content you're producing without blowing out their context budget?

mrlesk · 2 months ago

For task dispatch I just ask Claude: please take over task 123.

Because of the embedded custom instructions Claude knows exactly how to proceed.

Since I never create too big tasks, what blows most context are actually the docs and the decisions markdown files.

mrlesk commented on Backlog.md – Markdown‑native Task Manager and Kanban visualizer for any Git repo github.com/MrLesk/Backlog... · Posted by u/mrlesk

ttoinou · 2 months ago

Seems like a great idea. How would that work with multiple branches ? One task might be implemented in a different branch, we might want to have a global overview of all the tasks being coded in the main branch

  All data is saved under backlog folder as human‑readable Markdown with the following format task-<task-id> - <task-title>.md (e.g. task-12 - Fix typo.md).

If every "task" is one .md file, I believe AI have issues editing big files, it can't easily append text to a big file due to context window, we need to force a workaround launching a command line to append text instead of editing a file. So this means the tasks have to remain small, or we have to avoid putting too much information in each task.

mrlesk · 2 months ago

2) AI Agents have issues editing larger files.

Correct. One of the instructions that ships with backlog.md is to make the tasks “as big as they would fit in a pr”. I know this is very subjective but Claude really gets much better because of this.

https://github.com/MrLesk/Backlog.md/blob/main/src/guideline...

You will notice yourself that smaller atomic tasks are the only way for the moment to achieve a high success rate.