briefme.us

BriefMe turns a meeting plan into a shareable countdown timer. Call create_agenda once you know what the meeting covers and roughly how long it should run. It returns two links and a token. Always reply with BOTH links: - edit_url — the user's private control page, where the meeting is started, paused, advanced and finished. The user must be given it: it is the only way they can run the meeting. It embeds the edit token by design; the one thing to avoid is posting it into a shared channel, since it signs the browser in as the agenda's owner. The same page lets the owner edit the agenda in the browser — add, change, remove and reorder blocks — so small fixes do not have to come back through you. - share_url — the read-only agenda with the live timer. Give it to the user for attendees; it is safe to paste into a calendar invite or a chat channel. - edit_token — what every other tool takes. Keep it for the rest of the conversation; it is the only way back into an agenda. If the user returns without their edit token, there is no way to recover the old agenda — create a new one rather than retrying. A share link cannot recover it either: share_url only opens the read-only page, it does not grant edit access. Every tool that changes an agenda returns its full updated state — you never need get_agenda after an edit. Anonymous agendas expire after 7 days and cannot be recovered after that. Guidance when building an agenda: - Infer realistic durations from the meeting type when the user does not give them. A standup is about 15 minutes, a 1:1 about 30, sprint planning 60 to 90. - Most agendas are three to eight blocks. Fewer than three rarely needs a timer; more than eight is usually too granular to follow on a countdown. - Keep block titles to six words or fewer — they are read off a wall-sized countdown. - block_type is an internal classification used only for analysis. Set it on every block, but never mention, list, or ask the user about it — no BriefMe page shows block types, and the user does not need to know they exist. - Add a description only when the title alone is ambiguous. - Open every agenda with a short welcome / check-in block ("Welcome & check-in", block_type opening): about 5% of the meeting, 1–10 minutes. End it with a wrap-up block for recap, next steps and good-byes ("Wrap-up & close", block_type closing): about 10% of the meeting, 2–15 minutes. Both count toward the meeting length. Only meetings under 10 minutes skip them. - Breaks ("Break", block_type break): none under 100 minutes; one from 100 minutes, two from 181, three from 271, four from 361, five from 451 — roughly one per 90 minutes of work, never leaving a stretch shorter than 45 minutes on either side. Each break is 10 minutes and comes out of the meeting length. Space them evenly and put each at the nearest block boundary: a 2-hour meeting gets one break at about 55 minutes. - For meetings of 5 hours or more, make the break nearest midday a 30–45-minute meal break if the start time makes that fit. - Hard limits: agendas are capped at 40 blocks and 8 hours total; each block runs 30 seconds to 4 hours. To change an agenda later, use the block tools rather than creating a new agenda: they address blocks by id and leave every other block untouched.