Gain access
Features

Every gap, filled.

From the first rough Draft to the last merged PR, here is everything Tinkerbee does with your Spec.

Specs

Write it rough. Read it right.

A Spec says what you want built, in plain words, under an ID like SPEC-12. You write it in a rich editor, next to its Flow, ERD fit, Glossary and Todos tabs.

Why it matters. What you meant lives on one page, not across five threads.

Grill rounds

Questions before code.

Press Grill. Tinkerbee reads the Spec and your code, then lists what is missing as Open Questions. Each one comes with options and a recommended pick.

Why it matters. The gaps get answered before your agent starts, so it has nothing to guess.

Decisions

Answers that stay answered.

Pick an option or write your own answer. It becomes a Decision, and the next grill round builds on it. Defer what can wait, and say why.

Why it matters. Each choice has a name and a reason, so nobody makes it twice.

Glossary and ADRs

One word. One meaning.

Each repo gets one Glossary, with the words to avoid. On connect, Tinkerbee imports your GLOSSARY.md and ADRs, or suggests them from the code for the owner to approve.

Why it matters. When the Spec says Refund, your agent knows which Refund.

ERD and chat

Ask your schema anything.

Tinkerbee infers an ERD from your code at each commit. Ask it why a table points where it does. Pin a note to an entity and it carries over to the next snapshot.

Why it matters. You check the Spec against the data you have, not the data you remember.

Flow and ERD fit

See it from every side.

The Flow tab draws the Spec as steps. ERD fit checks it against your schema. Both raise their own Open Questions.

Why it matters. A missing branch costs a minute here and a day in review.

Comments

Pick at it together.

Highlight any line to start a thread. Reply, resolve, @-mention a teammate, or turn the comment into an Open Question.

Why it matters. Review happens on the Spec, right next to the words.

Todos

Homework, with names on it.

Todos track the work a Spec needs before it is done, like asking finance or reading a policy. Each one has an owner. My Todos lists yours across every repo.

Why it matters. Every loose end has an owner before sign-off.

Ready and freeze

Ready means ready.

Sign off once no Open Question is left. The Spec pins to a commit and stops moving. Once it has tickets, it is final.

Why it matters. The Spec your agent builds from cannot change under it.

Tickets

Cut thin. Served in order.

A Ready Spec splits into thin tickets in blocked-by order, each marked AFK or HITL. A drift check first asks about code that moved since sign-off. Copy them as Markdown today. Send them to Knol soon.

Why it matters. Each ticket fits one agent run and says what it waits on.

PRs and Mark Shipped

PRs find their Spec.

Put the Spec ID in a PR body and the PR links itself. When every PR is closed, Tinkerbee nudges you to Mark Shipped, and the new terms and ADRs join the repo.

Why it matters. The Spec ends where the code ends, with nothing left hanging.

MCP server

Your agent reads the Spec, not your mind.

A read-only MCP server gives Claude Code, Cursor and Codex the Spec with its Decisions, Glossary terms, ADRs and tickets. Agents sign in with your GitHub and see only your repos.

Why it matters. The answers travel with the work, so your agent never has to ask.

Inbox and push

News that finds you.

You watch the Specs you touch. One inbox covers every repo. Browser push is opt-in, for @mentions and Todos assigned to you.

Why it matters. You hear what changed without checking every Spec.

Token caps

Tokens, by the seat.

Each editor seat gets a monthly Token cap. Only the seat that runs out pauses. Team & billing shows usage per seat and per Spec.

Why it matters. One busy teammate never stops the rest. Writing, comments and MCP reads keep working.

Roles

Access follows GitHub.

If you can see the repo on GitHub, you can see its Specs. Owners make others editors or commenters. Lose access on GitHub and you lose it here too.

Why it matters. There is no second list of people to keep in sync.

Ready when you are.

Tell us about your team and what you want to build. We will get you in.

Gain accessBeta access. We approve every account by hand. Or email us