Small tickets. AI builds them. Review agents bring them to Done.

Tick-it plans your work into small tickets, hands each one to an AI coding agent (Claude Code today), and has review agents steward every pull request through to merge and deploy. You see the time and cost of every ticket and epic as it happens.

Get notified See how it works

acme/checkoutEpic: Saved cardsbuild $4.18review $3.02fix $0.71

Backlog2

Card expiry remindersTCK-421M
Default card settingTCK-420XS

Ready1

Remove a saved cardTCK-419XS

In progress1

Save card on payTCK-418S$1.84Building · 12 min

In review1

Card list on AccountTCK-417M$3.12Review round 2

Done1

Store card tokensTCK-416S$2.95Merged · deploy checked

Example data. On a real board each card is a ticket in your repository.

How it works

Everything between an idea and a checked deployment

Every ticket goes round the same six steps. Agents do the work at each one; a person comes in to approve a plan, answer a question or sign off a deploy.

Plan
AI drafts the epic, a person approves it
Small tickets in build order, each sized XS to L with acceptance checks. Tick-it flags one that's too big and suggests a breakdown.
Saved cardsApproved by @rhea
Wave 1
TCK-416Store card tokens S
TCK-417Card list on Account M
Wave 2 · after 416
TCK-418Save card on pay S
Build
An agent takes the next ticket
On your machine or in the cloud. It gets the brief, the checks and the memories that apply, and opens a pull request.
```
> /tick-it take TCK-418
Brief · 4 acceptance checks · 2 memories
Building on tck-418-save-card-on-pay
Opened PR #318
```
Review
Review agents send it back until it's right
Blocking findings start a fix round. Optional ones become proposed tickets. Rounds stop at a clean pass or the size’s budget.
BlockingCard token logged at info level
FixedRound 2
OptionalExtract the card form into a component
CleanRound 3 · $1.21 of $3.00
Merge
The queue rebases, waits for CI and merges
In order, with your merge checks: which check must pass when certain files change, and what fixes it when it fails.
1 · Merging nowPR #318 Save card on pay
2 · WaitingPR #321 Remove a saved card
CI passedMigration numbers
Deploy
Checks that only pass in production
Mark an acceptance check for after deploy. Once it ships, evidence is recorded and a person signs it off.
PassSaved card charges in live Stripe
Evidence recorded by the agent
Awaiting sign-off
Remember
The next session starts knowing more
Decisions, conventions and gotchas, stronger each time they help a ticket merge cleanly, and flagged when their files change.
M-87 · gotchastrength 0.74
Card tokens never reach logs; use the redacting logger in lib/log.ts.

The whole loop, step by step →

Costs

You'll know what every ticket cost

Every agent run is priced as it happens and split into building, reviewing and fixing. Read it by ticket, epic, person or model.

Review budget by size$1 · $3 · $5XS, S and M: the 75th percentile of what finished tickets spent

A typical S ticket$1.54Median review and fix spend across 119 tickets

Monthly capPer personPause, warn, or ask an admin when someone reaches it

How costs and budgets work →

TICK-IT
acme/checkout

TicketTCK-418 · S

TitleSave card on pay

Build · 1 session$0.92

Review · 3 rounds$1.21

Fix · 2 rounds$0.33

Total$2.46

Time to Done41 min

Merged · deploy check signed off
Example ticket

What needs you

You're only asked when a person is needed

Everything waiting on someone lands in one list, across every repository: a question from a session, a review that won't come clean, a plan to approve, a deploy to sign off.

Tick-it for teams →

Needs you3

TCK-417 Card list on AccountQuestion from the session: show expired cards, or hide them?

TCK-418 Save card on payAfter-deploy check waiting for your sign-off

Epic Refunds@sam asked you to review the plan

Also in Tick-it

Built for a team shipping with agents every day

Milestones and roadmap

Group epics into releases people would notice and work them in order.

Proposals from reviews

Optional findings are grouped into tickets you can create or dismiss in one go.

Retrospectives

For each epic and milestone when it finishes, and daily if you want, with findings you can turn into tickets.

Before and after pictures

A change to what people see carries pictures, posted on its pull request.

Teams and roles

Owners, admins, members and viewers, by repository or organisation.

Import from GitHub

An agent reads and sizes your open issues and turns them into tickets.

All features →

Where you use it

In your agent, in the browser, and on GitHub

The Claude Code mod

The board, the ticket's brief, the size budget and stewarding, beside your session.

> /tick-it add S Add a README badge
Created TCK-212 · S · Ready

The web app

Home, the board, epic plans, the merge queue, agent sessions, proposals, costs and memory, for the whole team.

app.tick-it.dev/r/acme/checkout
  Board · Epics · Merge queue
  Proposals · Costs · Memory

The GitHub App

Follows each pull request and its CI, moves the ticket when it merges, and posts before and after pictures for a change people can see.

PR #318 merged
TCK-212 → Done
  3 checks passed · 1 review round

Integrations →