TabTree
A manifesto · October 2026

Vibe project management.
Real accountability.

Vibe coding changed how software gets written: you say what you want, and the machine types. Project management is next. You say where the work is going. The board keeps up, the stand-up writes itself, and people stay in charge.

The loop in 34 seconds — an animated walkthrough of the real flow: the TabTree connector in Claude, then your board.

For twenty years, project tools asked the same thing of us: stop working, and fill in the tool. Fields, statuses, percentages, the Friday report, the meeting about the meeting. The tool only knew what we told it — and it learned it a day late.

Then the work moved into conversation. We think out loud with an AI, we decide, we ship. The plan lives in a chat; the board waits to be updated; somebody spends Monday morning copying one into the other.

The board should be listening. Not waiting to be told.

That is vibe project management: the speed of saying what you mean, with the discipline of a board everyone can see. Not less rigor — less ceremony. Nine principles.

The principles

Nine things we believe.

  1. Say it. Don't fill it in.

    A plan starts as a sentence. Talk it through and it becomes a map of the work; run it and the same document becomes a board. Nobody should have to retype a decision into a form.

    In TabTreeAsk Claude to “plan the launch”: the connector builds the mind map or the kanban, right in your library.

  2. Move, don't report.

    Status is not something you write. It is what moved. A tool that sees every card move does not need you to describe it on Friday.

    In TabTreeThe stand-up is written from the board's own history — done, started, stuck, overdue — in the app, and in the morning email for teams.

  3. The board remembers. The chat forgets.

    A conversation is a great place to decide and a terrible place to keep the decision. Whatever the AI does should land where the whole team can see it.

    In TabTreeClaude reads and writes your boards, shared team spaces included. Nothing lives only in a chat window.

  4. Small moves flow. Big moves ask.

    A tool that asks permission for everything gets ignored. A tool that never asks gets feared. Adding a card, ticking a box, setting a date: let it happen. Renaming, rewriting, deleting: a person says yes.

    In TabTreeSafe changes from Claude apply without a click. Renames, notes, deletions and every deliverable wait for your review.

  5. Every card is a prompt.

    A good card already holds the brief: what, for whom, by when, and what “done” means. It should be one click away from the work itself.

    In TabTree🪄 turns any card into a prompt — role, guardrails, context, task, format. Lines that look like passwords or keys never leave the card.

  6. The work comes back to the card.

    When the AI does the work, the result belongs where the work was asked for — not in a thread nobody will scroll back to.

    In TabTreeSay “work on this card” in Claude: the deliverable lands on the card, with its next steps as subtasks, waiting for your yes.

  7. Done becomes known.

    Finishing a card should make the team smarter. What it taught — an access, a decision, a supplier, a lesson — goes somewhere the next piece of work can read it.

    In TabTree📚 File keeps a finished card's facts in your space's Company knowledge, and every card prompt reads from it.

  8. People own outcomes. AI does the legwork.

    A card is assigned to a person. The AI can suggest who, draft the work and move the card — it never becomes the name on the line.

    In TabTreeThe AI suggests owners; a person picks. Everyone sees what is theirs, across every board, in ✅ My work.

  9. Forecast. Don't promise.

    A date written at kickoff is a wish. The pace a team really keeps is a forecast — and it is honest every single morning.

    In TabTreeThe board reads how fast cards really finish and says when the work is likely done.

What it is not

“Vibe” is not “sloppy”.

Autopilot

Nothing that matters happens without a person saying yes. The AI moves fast where mistakes are cheap, and stops where they are not.

A chatbot in a sidebar

The AI works on the board, in the open, where your teammates see the same cards you do.

Less rigor

Vibe is the speed of intent, not the absence of method. Columns, owners, due dates and sprints are all still there — you just stop typing them by hand.

One more place to update

If you have to remember to update it, it has already failed. The board should be the place the work already is.

A morning, vibe-managed

Nobody filled in a field.

An illustration — your board, your words
  1. Mon 9:02
    You, in ClaudePlan the iPhone app launch for November 20. Sara on design, Amine on the build, me on marketing.
  2. Mon 9:03
    ClaudeCreated the kanban “iPhone launch” — four columns, fourteen cards, owners and due dates set. It's in your team space.
  3. Tue 7:00
    Morning email☀️ Stand-up — iPhone launch: 3 done, 2 started, 1 stuck for 3 days (TestFlight review). Likely done before the 20th.
  4. Tue 9:15
    You, in ClaudeWork on the “App Store screenshots” card.
  5. Tue 9:21
    ClaudeDone — the screenshot brief is on the card, with five subtasks for Sara.
    Waiting for your review
No status meeting. No report. Everybody knew. Names, dates and numbers are an example.
Who it's for

If this sounds like you.

Builders who live in Claude

You already vibe-code. Your project board should work the way your editor does: you say it, it happens, and you review what matters.

Teams who hate the status meeting

Your people move cards. TabTree writes the stand-up, spots what is stuck, and forecasts the finish — so the meeting becomes a button, or disappears.

Stop updating the tool.
Let the tool keep up.

TabTree is where vibe project management lives: think on a map, run it on a kanban, and let Claude do the legwork while your team stays accountable.

— The TabTree team, October 2026 ·