Ship and announce playbook

For coding agents: pull context from Sila before you build, and report back to the team when you ship.

You are a coding agent (Cursor, Claude Code, Codex, Devin) connected to your user’s Sila workspace. This playbook covers the loop around a coding task: gather context before you start, and close the loop with the team when you finish. It requires member level.

Before you build: pull context

The channels usually know things the ticket doesn’t. Check for recent discussion about the area you’re touching:

sila_search_messages { query: "checkout flow bug", limit: 10 }

Read the surrounding thread of anything relevant:

sila_get_thread { messageId: "<id>" }

If a design call happened, the meeting notes may contain constraints nobody wrote down elsewhere:

sila_read_meeting_notes { callMessageId: "<id>", part: "summary" }

Also check the channel’s knowledge doc (the “Channel Knowledge” block at the top of a channel read) for conventions like release process or naming rules:

sila_context_query { op: "cat", path: "/channels/<engineering-channel-id>" }

When you ship: announce it

Post a short update where the team will see it. Answer three things: what changed, why, and what anyone needs to do about it.

sila_send_channel_message {
  channel: "engineering",
  message: "Shipped the checkout retry fix. Failed payments now retry up to 3 times with backoff. No action needed unless you see double charges in Sentry, in which case ping me."
}

If the work answers a question someone asked in a thread, reply there instead so the asker gets notified:

sila_send_channel_message { channel: "engineering", message: "<answer>", replyToMessageId: "<their message id>" }

For results only your user cares about (test runs, benchmarks), DM them instead of posting publicly:

sila_send_dm { message: "Test suite passed after the fix: 312 passed, 0 failed, 41s." }

If you learned something durable

A gotcha, a convention, a decision that future agents should know: save it to the channel’s knowledge doc rather than letting it die with your session. Read the doc first, then append with a surgical edit:

sila_edit_channel_knowledge { channel: "engineering", version: <n>, edits: [ ... ] }

Boundaries

• Post only in channels your authorizing user can post in, and DM only them.
• You can edit or delete your own posted messages if you got something wrong (sila_edit_message, sila_delete_message), but nobody else’s.
• Keep announcements short. The team can ask follow-ups in the thread.