1
Write a plan in markdown
Start with a markdown plan — features, bugs, ideas. Vibstr turns each item into a tracked ticket automatically.
Live softwareThe tracker the AI talks to.
Vibstr is a build tracker designed for teams coding with Claude, Cursor and other AI tools. Plans become tickets. Context travels with the work. Commits close the loop.
Why we built it
Built for the way AI development actually works.
We got the email everyone dreads — VivifyScrum was shutting down. Time to find a new project management tool.
We looked at all the obvious alternatives. Some were good. Most were fine. None of them made sense for how we were actually working, which by that point was: write a plan in markdown, hand it to Claude, review the output, iterate fast, ship. The classic swim-lane board — built for a team moving sticky notes around a wall — wasn't designed for a planning-to-build cycle that now happens in minutes, not sprints.
The friction was always the same. You'd have a clear idea of what needed doing. Claude would write solid code. And then you'd spend twenty minutes updating tickets that no longer reflected what had actually happened. The tracker and the work had separated. Living in different realities.
We decided to fix it for ourselves first. Eat our own dogfood, see if the idea held. The core question was simple: what if the tracker understood the way AI-assisted development actually works — where plans become code becomes commits, fast, and the context needs to travel with it?
Vibstr is the answer we came up with. It's not trying to replace Jira. It's built for a different kind of work.
What it is
A tracker that keeps up with how you actually build.
Vibstr turns markdown plans into trackable items, keeps the AI context attached to each one, and closes work automatically when you commit. The build history, the prompt, the changelog — all in one place.
Less time updating boards. More time building things.
📝
Markdown plans become ticketsWrite a plan the way you think. Vibstr structures it into items you can track, assign and close.
🤖
AI sidebar reads the contextClaude and Cursor see the open item and the history. No more copy-pasting context into every prompt.
🔗
Commits close the workReference a Vibstr item in a commit and it closes automatically. Build log, prompt and changelog stay linked.
💬
Slack syncs both waysDiscuss in Slack, see it in Vibstr. One conversation, not two.
How it works
Plan. Build. Ship. Repeat.
2
The AI sidebar reads the context
Claude and Cursor can see the open item, the history and the codebase state. No copy-pasting context into every prompt.
3
Commits close the work
Reference a Vibstr item in your commit and it closes automatically. The build log, prompt and changelog stay together.
4
Slack keeps the team in the loop
Threads sync both ways. Discuss in Slack, see it in Vibstr. One source of truth without forcing anyone to change tools.
Who it's for
Teams building with AI tools who hate updating their tracker.
Vibstr is for developers and small teams who are already using Claude, Cursor or similar AI coding tools and find that their project management setup hasn't kept up.
If the gap between what you're building and what your tracker says you're building keeps growing, Vibstr is for you.
Where it's at
Live and in use. We build Vibstr with Vibstr.
Vibstr is live at vibstr.app. We use it every day to build all four Custard Square ventures. If it breaks, we feel it first.