01
Sprint wrap-up.
Wrap up the sprint.
TasksReported what shipped and what slipped
DocsDrafted the retro notes
CalendarFound an hour for the retro
Notes ready. The invite waits for you.
Engineering Managers
Less admin. More engineering.
One workspace. One AI, Chief, across all of it.
Free to start.
What is blocking the release?
Waiting for your yes
The work around the work.
The same list. One ask each.
Walk the board to see what moved.
What moved since Monday?
9 cards to Done. 2 slipped.
Scroll chat for questions nobody answered.
Anything unanswered?
3 questions. Oldest from Tuesday.
Juggle four calendars for an incident review.
Incident review with on-call.
Wed 2 pm works for all four.
Waiting for your yes
Write sprint notes from scratch.
Draft notes from these bullets.
Drafted and formatted.
Turn chat asks into cards by hand.
A card from Mei’s message.
In Backlog. Assigned to Mei.
One request. Several apps. One result.
01
Wrap up the sprint.
Notes ready. The invite waits for you.
02
Turn today’s #release asks into cards.
Four cards. Nobody retyped anything.
03
Set up the review for last night’s outage.
Doc and agenda ready. Invites wait.
04
Map the services sheet as a flow.
A flow and a deck. Both editable.
These always wait for you.
After each change, Chief re-reads it. If something did not land, it tells you.
Waiting for your yes
Chief reports how boards in Tasks are tracking, turns Chat messages into cards, books reviews in Calendar and drafts notes in Docs.
No. Sending, sharing and deleting always wait for your yes. You see what will go out, to whom, and can edit it first.
After a change, Chief re-reads what it wrote. If a change did not land, it tells you instead of claiming it did. Every step it took is listed in the thread.
Chief updates cards when you ask. It lists every change it made, then re-reads the board to confirm it. Deleting a card always waits for you.
Bring a real task. See it done.