How we ship
Vibstr is built for the AI-first dev workflow.
Plans derive items. Items know context. Code closes them via commits. Slack for talk, Vibstr for ship.
If you're a solo dev or a small team using Claude Code, Cursor, or Copilot daily, this is for you. If you're a 20-person org running Jira with a process committee, it isn't.
What "built for the AI-first workflow" means concretely: write a markdown plan, derive items from it deterministically (zero AI cost) or with one AI call. Open the per-item AI sidebar with a — it already knows the item, its linked plan, sibling items, comments, activity, and any GitHub PRs that touched it. Close items by pushing a commit with closes #42 in the message; the ingest endpoint parses it and flips the item to done. Discuss in Slack via a one-click thread; replies mirror back as comments. The four pieces work together. None of them try to be the conversation surface.
What you get without trusting us
- Your data exports as JSON or CSV any time. Never locked in.
- BYO Anthropic key. We never see your AI bill.
- Public shipped log (coming): every week, here's what shipped.
- No upsells, no surprise charges, no enterprise sales calls.
Try it. If it works, pay us. If not, turn it off.
Coming from VivifyScrum?
VivifyScrum is shutting down. The migration importer is live — upload your sprint columns export, map columns to status, hit Import. Five minutes.
Where to start
Quick start
Sign up, create a project, log your first item, and copy your first prompt. Five minutes.
Read →Claude Code integration
Drop one snippet into CLAUDE.md, ship a build, watch items close themselves via closes #NN.
Plans
Write a markdown plan, derive items deterministically or with AI, link the plan to a build. The pattern Vibstr was built on.
Read →Per-item AI sidebar
Press a. The sidebar already knows the item, its plan, sibling items, comments, activity, and GitHub PRs. Read tools auto-execute. Write tools approval-gated.
Discuss in Slack
One-click thread on any item. Replies in Slack mirror back as comments — edits and deletes too. No chat surface inside Vibstr.
Read →Generic git hooks
Not using Claude Code? Universal post-commit script in bash, PowerShell, or GitHub Actions. Ship to Vibstr from any workflow.
Read →Best practices
Labels-as-stages. The plan-driven ship loop. Anti-patterns to avoid. How we ship Vibstr with Vibstr.
Read →External automation (Path A)
HTTP endpoints any client can drive with a project API key. Plan creation, item bulk-create, ship endpoint, comment bridge.
Read →Pricing
14-day free trial, no credit card. Then $2.99/seat/month for unlimited workflow features. AI requires your own Anthropic key. We never mark up AI compute. You pay Anthropic, not us.
Read →Onboarding
The 5-step first-run tour. Connect Claude Code is one master snippet — copy, paste into Claude Code, tell Claude to add it to CLAUDE.md. Trial-day-N nudges. Replayable from Settings any time.
Read →Migrate from VivifyScrum
Upload your sprint columns JSON, map columns to status (defaults preserve workflow stages as labels), hit Import. Tested against real 51-item sprints.
Read →How Vibstr compares
Vibstr vs Linear
Linear wins on polish, cross-functional fit, and team scale. Vibstr is built for solo and small-team devs using Claude Code daily. Both legitimate.
Read →Vibstr vs Jira
Jira wins on configurability, ecosystem, and enterprise scale. Vibstr is built for zero process weight and AI-native workflows. Pick what fits.
Read →Vibstr vs Notion
Notion wins on flexibility, docs-plus-database fusion, and team workspace. Vibstr is purpose-built for shipping code with AI. Different shapes, both useful.
Read →Vibstr vs VivifyScrum
VivifyScrum got Scrum-first UX right — and is shutting down. We built a working importer. If your team isn't running classical Scrum, Vibstr fits.
Read →How the loop works in practice
The four primitives — item, plan, build, project — are the whole vocabulary. No sprints, no points, no portfolio dashboards.
- Items are the unit of work. Bug, feature, polish, test, schema. Three statuses (open, checking, done). Labels carry workflow stages. The Board view pivots on any field — labels, assignee, build, priority.
- Plans drive items. A markdown plan can derive items deterministically (canonical format, zero AI) or via AI (freeform text, one daily call). Items linked back to the plan show progress.
- Builds close items. Every closed item lives inside a build. The build carries a version, a commit hash, the prompt, and an auto-generated changelog.
closes #42in your commit message closes item #42 via the deterministic parser — no AI credit burned. - The AI sidebar is the first responder. Per-item context envelope means the AI already knows what's in the item, its plan, its siblings, comments, activity, and GitHub PRs. Read tools auto-execute. Write tools render an approval card.
Read the quick start to feel the loop in five minutes.
A note on voice
These pages are written for people who know what git push does. We don't bury the curl, we don't bury the schema, and we don't pretend everything is magic. Where the product is opinionated, we say so. Where it doesn't yet do something, we say so. If you spot a fib, file an issue.