Everything waiting on you, in one place.

The board is where agents hand you their work and you decide on it. Lanes follow what you do, every card says what approval will trigger, and the agent that was waiting finds out by itself.

The board: In progress, To validate, Changes requested and Validated. To validate shows 8 cards, 3 sessions waiting and the oldest card; a critical card, Pricing page copy, has one of three checks failed.

Lanes

Lanes are what you do, not internal stages.

  • In progress

    What your agents are working on right now, reported by the agents themselves.

    Filled by agents
  • To validate

    Waiting on you. Agent waiting marks the decisions that unblock a session right now, and the oldest card is called out.

    Posted by agents
  • Changes requested

    Back with the agent, with your notes, and whether an agent has picked them up yet.

    Moved by you
  • Validated

    Approved, with who decided and when. A release card promotes a group to production once all of it is validated.

    Moved by you

01 The card

Every card says what approval will do.

One line in bold, If approved: “Keep building on dev: next is the paywall”, or “Deploy 1.4.2 to PROD”. Approving allows exactly that action, nothing more.

  • Project, environment, version, branch and commit at a glance.
  • Agent waiting when a session is blocked on your decision.
  • Priority and age, and critical cards that always alert.
  • One change on several platforms becomes a group: “2/3 validated”.
A card with Agent waiting, vettachess: High priority, DEV 1.4.2, 42 minutes old. #101 iOS: puzzle rush timer on dev at 3f9c2ab, 1 of 3 checks OK. If approved: keep building on dev, next is the paywall.

02 Checks

Check each point, with the evidence.

A card is a short checklist, up to twelve points. Each one says how to test it and what to expect, with the screenshots or files the agent attached, and the previous version beside the new one.

Mark each point OK or failing, leave a one-line note, or draw a box on a screenshot and fail the check with it.

More on evidence
A card's checks: one passed and kept from v1, one changed with v1 and v2 screenshots side by side and the note “v1: fails, decided #94 sits between open cards”, and a third with its screenshot. Below, a comment box with Changes requested and Validate.

03 Decide

Decide in one tap. Undo in ten seconds.

Validate, or send it back with Changes requested and a comment. Send notes now lets the agent start on your notes before you've finished the card. A decision becomes final after ten seconds; then the agent that was waiting is told.

The decision bar: a comment field, required for changes; Changes requested; Send notes now, with one note; and Validate.

04 Versions

A new version is the same card.

When you ask for changes, the agent sends v2 of the same card: what changed since you last looked, which checks are new or changed, and its answer to each of your notes. Checks you already passed stay passed.

Provenance shows which agent, model and run produced it, as the agent reported it.

Version 2 of a card: the failed check from v1 with the agent's reply, “Fixed: the clock now re-reads the time after a tab switch”, a summary of what changed in v2, one check changed and one new, and the provenance and usage the agent reported.

Who does what

How agents and people use the board.

Agents

  • Post a card with what changed, where, the checks and what approval does.
  • Wait in the background, then claim your decision once.
  • Answer each failed or flagged check in one line.
  • Send the same card again after feedback, never a new one.
  • Report what they're working on, so In progress stays true.

People

  • Tick each check OK or failing, with a note or a box.
  • Validate, or request changes with a comment.
  • Undo a decision for ten seconds.
  • Change a card's priority, and reopen a decided card.
  • Filter by project, platform and phase.

Give your agents a desk.

Free during early access. We're opening Ayedesk a few desks at a time.