mrlesk

6 ms·

1.
Senior AI Agents: True Intelligence Is Instructions Discovery(mrlesk.com)
3 points by mrlesk 8mo ago|0 comments
2.
Show HN: Agents Council – Connect Claude, Codex, and Local Agents via MCP(github.com)
3 points by mrlesk 8mo ago|0 comments
3.
Steer vs. Delegate: Two emerging ways to use AI agents(mrlesk.com)
1 points by mrlesk 9mo ago|1 comments
4.
by mrlesk 9mo ago
Steer mode helps you ship faster as an individual. With Delegate you'll use AI more like a team lead. Should you use one, the other or both?
5.
by mrlesk 1y 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 thi
6.
by mrlesk 1y 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
7.
by mrlesk 1y ago
Thanks. Let me know if you have any feedback
8.
by mrlesk 1y ago
Didn’t know this tool. Thanks for sharing
9.
by mrlesk 1y ago
I made it configurable and autoCommit is false by default
10.
by mrlesk 1y ago
Never heard of taskwarrior. I will check it out. Thanks for sharing
11.
by mrlesk 1y ago
Yep. Dependecies are supported via —dep parameter. Will check the 404 issues. Thanks for reporting it
12.
by mrlesk 1y 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
13.
by mrlesk 1y 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 decis
14.
by mrlesk 1y 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
15.
by mrlesk 1y ago
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 b
16.
by mrlesk 1y ago
Hehe. It was a veerry lucky situation. I sent a message to someone telling that I was working on backlog.md and it turned the name into a link automatically. I wanted to remove the link and I clicked on it accidentally and discovered that n
17.
by mrlesk 1y ago
Yep. I’m happy to hear that more and more people are converging towards a very similar process as this ends up being the most productive.
18.
by mrlesk 1y ago
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
19.
by mrlesk 1y ago
Will definitely do. I am also planning to run a benchmark with various models to see which one is more effective at building a full product starting from a PRD and using backlog for managing tasks
20.
by mrlesk 1y ago
You’re absolutely right Joking aside there is a npm/bun install -g backlog.md at the top but I can add an extra one in the 5 min intro. I am using Bun’s new fullstack single file builds. I’m really impressed by how easy it was to set u
21.
by mrlesk 1y ago
For such kind of tasks I would go with Taskmaster AI. It had mcp integration and probably could connect with jira. Backlog is more for smaller projects where you wouldn’t normally have a project management tool
22.
Backlog.md – Markdown‑native Task Manager and Kanban visualizer for any Git repo(github.com)
254 points by mrlesk 1y ago|62 comments
23.
by mrlesk 1y ago
I 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 %