One ticket, from a line to your agent to a checked deployment
Every ticket in Tick-it goes round the same six steps. Agents do the work at each one. A person comes in only to approve a plan, answer a question or sign off a deploy.
- Plan
AI drafts the epic, a person approves it
- Describe the outcome; the agent drafts an epic of small tickets in build order, grouped into waves by what each waits on
- Each ticket has a size (XS, S, M or L) and acceptance checks a reviewer can tick off
- A teammate who can accept plans approves it, or asks for changes as suggestions on the plan
- Changing a ticket after approval puts every approval back to requested
Saved cardsApproved by @rheaWave 1TCK-416Store card tokens STCK-417Card list on Account MWave 2 · after 416TCK-418Save card on pay S - Build
An agent takes the next ticket
- Take a ticket in Claude Code with /tick-it, or start it in the cloud on your own claude.ai routine
- The session gets the brief, the acceptance checks and the memories that match the ticket and its files
- It opens a pull request and reports each run, so its time and cost are on the ticket
- A session that needs a person asks a question instead of guessing
> /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
- Your repository's own review skills read every pull request
- Blocking findings send the ticket back for a fix round; optional ones are grouped into proposed tickets
- Rounds stop at a clean pass, the size’s round limit or its review budget
- After several rounds in a row that each end blocked, Tick-it suggests breaking the ticket down
BlockingCard token logged at info levelFixedRound 2OptionalExtract the card form into a componentCleanRound 3 · $1.21 of $3.00 - Merge
The queue rebases, waits for CI and merges
- Reviewed pull requests join the merge queue in order
- The queue brings the next one up to date by rebase or by merging main, then waits for every check
- Merge checks name a check that must pass when certain files change, and the skill a session follows when it fails
- Merge automatically, or keep the last click for a person
1 · Merging nowPR #318 Save card on pay2 · WaitingPR #321 Remove a saved cardCI passedMigration numbers - Deploy
Checks that only pass in production
- Mark any acceptance check as one that can only pass after deploy, with the reason
- Once the ticket merges, the agent records pass or fail with evidence for each
- A person signs it off; a failure after deploy is confirmed and followed up as work
PassSaved card charges in live StripeEvidence recorded by the agentAwaiting sign-off - Remember
The next session starts knowing more
- Sessions keep decisions, conventions, gotchas and learnings, anchored to the files they describe
- A memory gets stronger each time a ticket that used it merges without a send-back, and weaker when a review names it
- When a merged change touches an anchored file, the memory is flagged for a re-check
- People confirm or retire what agents wrote
M-87 · gotchastrength 0.74Card tokens never reach logs; use the redacting logger inlib/log.ts.
Sizes
Small tickets, kept small
Size is how much a ticket changes, and it sets how long review may run and what it may spend.
| Size | For | Review rounds | Default review budget |
|---|---|---|---|
| XS | A copy change, a config value, one small fix | 2 | $1 |
| S | One behaviour in one area, with its tests | 3 | $3 |
| M | A feature across a few files or a page | 5 | $5 |
| L | Rare: usually a sign to break the ticket down | 6 | Rounds only |
Tick-it suggests a size from what similar finished tickets changed, with the risk of the areas a ticket touches. Owners can set their own budgets.
When a person is asked
Agents do the work; people make the calls
A person is asked to approve a plan before it is built, to answer a question a session can't settle from the code, when a review won't come clean inside its budget, and to sign off a check after deploy.
Each need goes to one list for the right person, who is told once. While an agent is still at work on a ticket, it isn't a need.
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