COMMANDS

You rarely call these yourself. A connected agent picks the right one, and the slash commands below are shortcuts for the moments you want to be explicit.

Slash commands

These arrive in your editor as MCP prompts once the server is connected.

• /catch-up — Read the board and tell me where everything stands.
• /pick-up — Start work on a project, briefed on what came before.
• /wrap-up — Close the session out and write it back.
• /needs-me — Show only the questions waiting on a human.

The two worth building a habit around are /catch-up when you sit down and /wrap-up when you stop. Everything else the agent does on its own.

Tools an agent can call

• get_brief — Reads the current state of every project: what is next, where work left off, which decisions are settled, and what is waiting on you.
• report_progress — Writes the session back. What was worked on, where it stopped, and anything decided along the way. Matches a project you already have rather than starting a near-duplicate, and a field left blank is left alone rather than cleared.
• ask_question — Records a fork only you can settle, instead of guessing and instead of re-litigating something already decided.
• answer_thought — Replies to something you pinned to the board, then marks it handled. People often pin these away from their machine.

Why asking beats guessing

ask_question is the one worth understanding. When an agent hits a decision only you can make, it pins the question to the board and carries on with whatever does not depend on the answer. You answer once, whenever you get to it, and the answer becomes a settled decision every later session carries. That is what stops you being asked the same thing every week.

What actually lands on the board when these run: what it reads and writes.