All I'm wondering is how did you secure the .md TLD?
Backlog.md – Markdown‑native Task Manager and Kanban visualizer for any Git repo
31–40 of 63 posts
Re: Backlog.md – Markdown‑native Task Manager and Kanban visualizer for any Git repo
#32I threw Claude Code at an existing codebase a few months back and quickly quit— untangling its output was slower than writing from scratch. The fix turned out to be process, not model horsepower. Iteration timeline ================== • 50 % task success - added README.md + CLAUDE.md so the model knew the project. • 75 % - wrote one markdown file per task; Codex plans, Claude codes. • 95 %+ - built Backlog.md, a CLI t…
Hey man amazing work! You’re a legend
Re: Backlog.md – Markdown‑native Task Manager and Kanban visualizer for any Git repo
#33Earlier quoted context omitted.
Would love more detail on your integration with claude. Are you telling claude to use backlog to plan X task? Feels like some MCP integration or something might make it feel more native? Though i've not had much luck in getting Claude to natively use MCPs, so maybe that's off base heh.
No mcp, just custom instructions. When you initialize backlog in a folder it asks you if you want to set up agent’s instructions like CLAUDE.md. It is important to say yes here so that Claude knows how to use Backlog.md. Afterwards you can just write something like: Claude please have a look at the @prd.md file and use ultrathink to create relevant tasks to implement it. Make sure you correctly identify dependencies…
How can I change from gemini to claude ?
Also I’m not fully sure about your setup. In my fresh pov I would next set up agents that check my github repo for backlog tasks and do pull requests on those tasks. If I write a good description and ideally tests I can optimize the results of these.
This creates the possibility of agents checking your backlog and prepare the work.
I usually work with aider everyday and I’m quite fast in achieving task, the next limitation would be the latency and some back and forth. I have some dead time in between. I can definitely define tasks faster than 1-1 AI.
Yeah if you could share a bit more how you do this with Claude we would all be thankful, also I havent seen anywhere to sponsor/tip you, would love to!
Re: Backlog.md – Markdown‑native Task Manager and Kanban visualizer for any Git repo
#34With aider you can run a second instance along with --watch-files and if you in your tasks do // #AI it will be added to the chat and with // !AI AI will then respond
so you can do
`backlog task create "Feature" --plan "1. Research\n2. Suggest Implementation// #AI AI!"` (yes weird order with the !)
and in the background aider will propose solutions.
I’m not sure how this compares to Claude Code or Codex, but its LLM-flexible. Downside is it doesn’t create a pull request. So it’s more helpful for local code.
I would probably add some Readme.md files to the --watch-files session and I think you need to click once [D]ont ask again so it wont keep asking you to add files
Re: Backlog.md – Markdown‑native Task Manager and Kanban visualizer for any Git repo
#35Ah, this is what the future after Jira looks like.
Re: Backlog.md – Markdown‑native Task Manager and Kanban visualizer for any Git repo
#36Seems 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- - .md (e.g. task-12 - Fix typo.md). If every "task" is one .md file, I believe AI have issues editing big files…
1) How will it work with multiple branches? Simple: using git :) Git allows to fetch certain files from other branches including remote ones without checking out those branches. The state is always up to date no matter if you are running backlog.md from main branch or a feature branch. It works well when there are not many branches but I need to check if I can improve the performance when there are lots of branches.
Nice, so there could be some kind of git kung fu command line to help with that. Maybe we could also have a separate folder using git worktree to post all the information in one branch. That'd duplicates all files though.
Another idea is to use git notes
Re: Backlog.md – Markdown‑native Task Manager and Kanban visualizer for any Git repo
#37I threw Claude Code at an existing codebase a few months back and quickly quit— untangling its output was slower than writing from scratch. The fix turned out to be process, not model horsepower. Iteration timeline ================== • 50 % task success - added README.md + CLAUDE.md so the model knew the project. • 75 % - wrote one markdown file per task; Codex plans, Claude codes. • 95 %+ - built Backlog.md, a CLI t…
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 e…
Yep. Dependecies are supported via —dep parameter.
Will check the 404 issues. Thanks for reporting it
Re: Backlog.md – Markdown‑native Task Manager and Kanban visualizer for any Git repo
#38Would love to be able to use this UI, connected to an external source like Linear.
Re: Backlog.md – Markdown‑native Task Manager and Kanban visualizer for any Git repo
#39This is a neat implementation, personally I use https://www.task-master.dev
Re: Backlog.md – Markdown‑native Task Manager and Kanban visualizer for any Git repo
#40How 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)