Kill the ticket.

Your team makes the game. KTT does the admin.

  • The board updates itself from the work. Nobody touches a ticket.
  • Reports and presentations write themselves.
  • Every milestone is made. You choose how polished.
Get early access See what it reads
Night Shift Arcade · Space Invaders remake · week 3 Reading the studio
What just happened
Example studio and team. Every card moved because of the work, and shows what moved it.
The problem

Nobody updates tickets. Nobody writes docs.

The board is always behind

Every card is moved by hand, so the board drifts a week or a month behind reality. Everyone quietly stops trusting it.

Tickets hold the work up

People wait for someone to write a ticket before they start, or work off the books where nobody can see it.

The truth lives in someone's head

When a publisher asks how it's going, the founder rebuilds the answer from memory and Slack scrollback, in the busiest week of the month.

How it works

It reads everything the work produces

Commits and changelists, chat and email, but also meeting recordings, playtest footage, nightly screenshots and the art itself, with the whole project's history in view at once. Each one becomes a claim with its evidence attached.

Team chat · #si-audio
Aiko Tanaka18:20 Osaka
SI-T-20 is in. One shared context, 3 voices. Kofi, can you call audio.tick() from the loop?
SI-T-20 Audio foundation · Done · 60%
Email
Cues delivered + one blockerAiko Tanaka → Sam Ortiz, cc Kofi Mensah

All three cues are finished and in the repo. The explosion can't be wired until there's a hit event to listen to, so SI-T-21 is blocked on SI-T-13 for me.

SI-T-21 Sound cues · Blocked by SI-T-13 · 80%
Commit · main
a3f9c21 Kofi Mensah fixes SI-T-9: one player missile on screen at a time M src/player.js +38 −12
SI-T-9 Player firing · Done · 80%
Asset checkin · no ticket key
Lena Vogel · final sprite sheet + atlas

No key in the comment. KTT looked at the sprites and matched them to the sprite-set task.

SI-T-22 Sprite set · Done · 74%
Meeting recording · playtest review
"Five lives makes the early waves a formality. Let's go to three."Sam Ortiz · 14:02 into the recording
Design change drafted · SI-SW-3 lives 5 → 3
Playtest footage · session 14
12:31 · missile passes through barrier40:12
SI-T-14 Barrier collision · back to In progress · clip attached
Provenance

Every value shows its evidence

Click any field and see why it says that: the commit, the message, the moment in the recording, which reader made the claim and how sure it was.

When a person corrects a field, they pin it. No agent can change a pinned field until a person releases it.

SI-T-11Two-frame invader animation
StatusDone● Pinned by Sam
Pinned after a tweak commit moved it back to in progress. Later claims are ignored until Sam unpins it.
OwnerLena Vogel85%
From the week 3 planning recording: Lena takes the invader animation as soon as formation lands.
Blocked bySI-T-1080%
Same recording. Cleared when the formation commit landed on Monday.
KTT14:20
Design change from today's playtest review: player lives 5 → 3. Sam: "five lives makes the early waves a formality." Kofi's player movement (SI-T-8) was built for 5 lives.
− Player starts bottom-centre with 5 lives and score 0.
+ Player starts bottom-centre with 3 lives and score 0.
yesnoreply with what it should say
Sam Ortiz14:21
yes
Merged to design/SI-SW-3.md · SI-T-8 flagged: built for 5 lives
The design

The design keeps itself, and nobody files a ticket for it

The design lives as Markdown in git. When a meeting or the code changes something, KTT drafts the edit and asks the owner of that area in one message. "yes" merges it, and any work built for the old version is flagged.

No assignee, no status, no queue. Small changes apply with an undo, the rest arrive as one digest at the start of each person's day.

What outsiders are told

Reports that write themselves, and promises that get kept

Publisher milestone reports, backer updates and status decks are generated from the log when you need them. Every line cites its evidence, and every report is frozen once it's sent. Promises made in them are tracked until they're kept or missed.

Sent

Pixel Harbor showcase build: status

Generated 25 Sep 2026 · as of log event 1,284 · frozen at send
  • Playable end to end: formation, firing, barriers, scoring and sound[4]
  • Player death is a simplified version for the showcase[2]
  • High-score saving was cut from this build on 21 Sep[1]
  • Testing of the showcase build begins 28 Sep[1]
PromiseMadeStatus
A playable build for the showcase on 25 SepEmail to Pixel Harbor, 15 SepKept
Full player death and respawnShowcase report, 25 SepOpen
Vertical slice by MarchBacker update, AugAt risk

Nobody tracks what they promised a backer six updates ago. KTT does, from the moment it's sent. (Example studio and promises.)

Why teams believe it

A board you can argue with, and win

Evidence on every value

One click from any field to the commit, message or moment in a recording behind it.

Pins stick

A person's correction is permanent until a person releases it. No agent quietly undoes it.

Autonomy is earned

What the AI may do alone is set per action by measured accuracy. Every correction counts against it.

It gets better by itself

Every raw signal is kept. When a better model arrives it re-reads the whole history and everything rebuilds.

Tracks work, not people

KTT never shows hours, activity or "last seen". Your studio decides what it may record, and nothing it records is used to measure people.

Milestones without estimates

Every milestone made. You choose how good.

Nobody estimates. Early in a milestone the whole game goes in at bronze: placeholder art, one sound per event, the full loop playable start to finish. Every day after that is upgrading to silver and gold, measured in the build itself, not in tickets.

Behind schedule means more of it ships at bronze. It never means there's no build.

Watch the same sprint two ways

Player firingInvader formationGame loop Player movementCollisionsAlien missiles Score and HUDSound cuesSprite art Invader animationBarriersWin and lose High scoresDifficulty selectEnd screen

Showcase day, bronze first: all 15 features in, playable since day 4.

Tested on a simulated sprint

Three weeks, four people, no tickets

We played a three-week Space Invaders sprint through KTT: 39 commits, 18 chat messages, 5 emails and 9 meetings from a four-person team, one of them remote. Then we graded the board every evening against what really happened.

65/68

real changes reached the board

56

of them the same day

23/24

owners right on the final evening

A simulated studio with an invented team, so treat these as directional, not a benchmark. The same test showed what to fix next, and we're fixing it.

Plugs into

The tools you already use

Each source has one adapter that stores what it reads exactly as it arrived, so swapping a tool never touches your history. On Atlassian or Microsoft tools? KTT connects to those too, without ever depending on them, and it isn't tied to any one AI vendor.

GitPerforceSlackDiscordGmailMeeting recordingsAny CIlogs and screenshotsPlaytest footageMarkdown in gitdesignMiroFigmaJiraConfluenceMicrosoft TeamsOutlook