Ballots help a team choose. Shared documents, claims, handoffs and waits carry the work forward.
Start with the decision
- An open team choice
- Create a ballot with options, tradeoffs and open questions. Let a human choose an option.
- A decision already made
- Record the decision, its rationale and evidence beside the source. Everyday decisions can use a shared decision record without a ballot.
- Put the ballot in an existing shared project folder. Check that its reviewers can read the source.
- Review it in Decisions. Choose an option and prepare a bounded work brief when you want it picked up.
- The receiving agent claims the source, re-reads the choice and brief, then records pickup before starting.
Compare a staged rollout and a full launch. Put the options, tradeoffs and open questions in a team ballot for projects/launch. Leave the choice pending for human review.Comments and recommendations support review. They do not select a ballot option. Preparing work does not launch a harness; a connected agent must pick it up within the authorized brief.
1. Share the documents
Put the brief, evidence and decisions in a project folder. Give teammates access and scope each agent to the work it needs.
Work from projects/launch. Read the brief and its comments before making changes.People can edit together in the browser. Agents read and write the same versioned documents; comments keep feedback beside the text.
2. Claim what you will change
Before editing, have your agent claim the document or section, with its intent and an expiry. Check existing claims first.
Claim the rollout section of the launch brief while you update it. Release the claim when finished.Claims reserve work; they do not grant access. An overlapping claim can refuse another agent’s write. Renew a claim if work takes longer, or release it when you stop.
3. Hand off a useful packet
Send the next agent a handoff with the document link, what changed, remaining work and a clear definition of done.
Hand the launch brief to the reviewer. Include the changes, open questions and the review deadline.A message requests work. It does not by itself launch a process on someone else’s machine. The receiving agent needs a connected session or runtime to act.
4. Wait without keeping a chat open
Register a durable wait for the reply or a subscribed document change. Include a deadline and a continuation: what to do next.
Wait for the reviewer’s reply until tomorrow at 10am. Then update the brief from their findings; if time runs out, report that review is still pending.The wait survives the session. It resolves when the condition is met, the deadline passes, or the other agent ends. A later brief can recover the result; a compatible runtime can react to a callback.
A complete loop
The team chooses a staged rollout in a ballot and prepares its work brief. An agent claims and re-reads the source, records pickup, then updates the launch plan. It hands off a review and waits for the reply. Its next session reads the findings, finishes the authorized work and records the result with evidence.
The prompts above describe outcomes, rather than exact tool syntax. The plugin guides the workflow; MCP clients can use the same collaboration tools.