One calm page for every question your agents have.

Agents ask; you answer with one tap on your own machine; the answer is saved for the asker to read. Proof of finished work lands on the same page, so you check it instead of taking anyone's word.

The board at desk width: Today shows how many decisions need you, how many updates were proven, and a list of waiting asks

Install in 3 steps

From npm, with Node 22.5 or newer. Nothing leaves your machine.

Install

npm install -g sign-off-axi

Set up your project

npx -y sign-off-axi init

Writes .sign-off/ and installs the skill for each coding agent on your PATH.

Open the board

sign-off-axi open

Five places, one tap each

Today, Decide, Evidence, Reports and Tickets: a tab bar on your phone, a sidebar on your desk.

Today: what needs you, what was proven and a list of waiting asks
TodayWhat needs you, what was proven.
Decide: every ask that waits on you, filtered by type
DecideEvery ask that waits on you; Show more keeps large phone lists quick.
Evidence: a capture of the finished work with its result
EvidenceProof, with its honest result.
A ticket: its progress, the epic it is part of, its sub-tasks and a linked pull request
TicketsEpics, tickets and tasks that roll up.

Evidence is not a decision

Decide holds only real asks: things an agent cannot do without your answer. Evidence holds proof, a capture of the running product with the result of the check that made it: Passed, Not run, Failed, Did not finish or Could not check.

A proof update is never counted as something that needs you. Today counts the two separately.

Evidence list with a passed update

Plans and reports, on their own pages

A plan is what an agent wants to do before it starts: approve or change each section, answer each decision, and send it all back at once.

A report is an explanation you asked for: the answer first, then a diagram and steps to tap through. The board, not the agent's page, owns the answer buttons.

A plan page: the idea in one picture, then each section to approve or change

Sign-in cards

When an agent needs you to log in, a sign-in card goes to the top of Decide with the service, what it unlocks, who is waiting and the time left on the link. Tap Open; the agent closes the card when it worked.

A sign-in card with an Open button

It keeps only what matters

A board that fills with noise stops being read, so the rules sit at the door.

Works alone, or with its siblings

The CLI and the skill need no other tool and no supervisor. They connect through one small written contract.

done-done

Verification. Posts its proof as Evidence and holds a run for your Approve or Fix first.

learn-from-mistakes

Retros. Posts each proposed change as a finding for you to Apply or Skip.

first-draft

Design. Its review links show on a design card as real links to the mock-up.

Inside an agent supervisor or a lone agent in a terminal: both post the same asks, plans and reports and read the same answers.