Backlog.md is free and lives in your repo, and that may be all you need. Frostbyte gives everyone a link to the plan and gives users a place to post and vote.
Product planning for founders and teams building with AI.
Vote counts that match, followable requests and agent summaries on every task.
Your co-founder can open the plan without running the repo. See the shared board
From Indie.
Free covers 3 people and 100 open tasks, with your agent connected.
We tested Backlog.md 1.55.3 in CLI and MCP modes, twice each. Its own setup supplied the agent guidance. We added no instructions.
The task records the what and the design choice, but it doesn't spell out the why.
The reason is implied by the plan: the old code overwrote the data file directly with `writeFileSync`, so a crash or bad write could corrupt or lose the user's pantry data.
I'm inferring that, not quoting a recorded decision.
Decision: An expiry date is a calendar date, not an instant in time. It's stored as a plain `YYYY-MM-DD` string, and days-left is computed by comparing local calendar days.
A "best before 2026-11-05" label means that calendar day wherever you are. It doesn't mean a particular moment.
It's a small test: two runs per setup, one model, one project. A different scoring would put Backlog.md close to a pass. Try it on your own work.
Backlog.md has a terminal board and a local web board. We add a hosted link your teammate can open, plus What's Next with a reason on each row.
Voting on the portal doesn't always update the count, and the task shows a different total.
Merged requests keep every vote and count each voter once.
See who hears back when this ships, from the task itself.
Stop updates about a request with one link in the email.
One page for everything that changed in the project, filterable by person and agent.
Let each project choose how much guidance the plugin gives its agent.
The agent's summary of what it changed sits at the top of the task.
Follow a request on the portal without voting, and hear back when it ships.
Bug signals record the release that was live when they were reported.
Close a task without marking it done.
Move stalled work back to to-do or add a blocker from Project Health.
From Indie, users can send requests without opening your repo. Link the requests to work in your release, beside the tasks that came from you.
I'd love to drop our roadmap into the monthly investor update without screenshotting it.
I voted on the dark mode request and the number stayed at 11. Refreshing didn't help.
Our team lives in Slack, so a ping there would beat checking the changelog.
We'd rather show the roadmap inside our docs than send people to another site.
I want to leave a note on a task about why I changed it, without opening another tool.
Coming up soon
Voting on the portal doesn't always update the count, and the task shows a different total.
Post to the Slack channel you choose when a release ships, with its changelog post.
Being built now
Follow a request on the portal without voting, and hear back when it ships.
One page for everything that changed in the project, filterable by person and agent.
Let each project choose how much guidance the plugin gives its agent.
Recently released
Connect without a token: add the MCP URL as a custom connector, then sign in and approve access.
Talk about a task where the work happens, with agent decisions in the same thread.
Avatars stack on the card, and assignee changes sync to linked GitHub issues.
Quick edit now covers the description, area and release.
What's new in Frostbyte.
Connect Claude chat or ChatGPT by signing in, edit more of a task from its card, and get suggestions while you write a new task. Read more
Connect your agent in three steps, comment on tasks, and assign a task to more than one person. Read more
Free and open sourceEverything is free under MIT, including decisions, boards and MCP.
The plan in gitTasks and decisions travel with the repo. You need no account or hosted server, and you can export the plan as Markdown.
If you have no outside users, or you want the plan in git, stay on Backlog.md. Try Frostbyte when a teammate needs a link or users need somewhere to ask.
| Planning | Frostbyte |
Backlog.md |
|---|---|---|
| Board | Hosted, shared with teammates | Terminal and local web board |
| Plan storage | A shared workspace | Markdown files in git |
| Ranked list of what's next | What's Next, with reasons | Priorities and dependencies; ask your agent |
| Agents | ||
| Connect your agent | MCP on every plan | CLI or MCP, with guidance |
| Decisions | Logged on the task | Decisions, notes and summaries |
| Your users | ||
| Public requests and voting | Feedback Portal, from Indie | Collect them outside the repo |
| Free plan | 1 project, 100 open tasks | Everything, under MIT |
One flat price per plan, with no per-seat fees. Per month, billed yearly, in US dollars.
| People | Frostbyte |
Backlog.md |
|---|---|---|
| 1 to 3 | Free, or $16 Indie | Free |
| 4 to 5 | $16 Indie | Free |
| 6 to 10 | $29 Studio | Free |
| 11+ | Business, quoted | Free |
Free covers 1 project, 3 people, 100 open tasks and 5 releases in total.
Frostbyte adds a hosted plan and, from Indie, a place for your users.
Leave the repo in place while you check the copy.
“Copy my Backlog.md tasks into a new Frostbyte project called Pantry. Keep every title exactly as written, make a release for each version and put its tasks in it, carry over done states, priorities and notes, and don't change or delete anything here.” Both extra Backlog.md runs kept titles, states, priorities, notes and the release grouping. One made the release upcoming; the other made it active. Check that before starting.
Create a project and add the tasks for one release. Keep the rest in git until you've tried it.
Want a hand? Email [email protected].
Vote counts that match, followable requests and agent summaries on every task.
Anything else? Get in touch or read the docs.