Planning sessions
Pressure-test a change plan before OrgBolt builds it. Type /planning and the AI asks one grounded question at a time — about the automation, access, and data your change actually touches — then writes up the decisions and risks so the build follows them.
What a planning session is
Most Salesforce changes fail on the things nobody thought to ask: the flow that already writes the same field, the profile that can't see it, the historic records a new rule would block. A planning session front-loads those questions. Before anything is built, the AI reads your org's real metadata and walks through what your plan touches, one question per turn.
Questions come with quick-answer buttons when the answer is a genuine either-or (press 1–9 to pick), and you can always type a free-text answer instead. The session runs right in the task chat, so everything you decide is part of the conversation the build turn reads.
Starting and ending a session
Type /planning in the composer (or press / to see all available skills, or accept the AI's offer when it spots a plan with real blast radius). The composer's Plan chip starts a Planning session too: on the dashboard it is lit by default, so a new Task opens as a planning session unless you switch it off before sending; inside a Task's chat, arm it, then send your message as usual. A start card marks the session; every turn inside it carries a slate border so you can see at a glance which part of the conversation was the planning session.
The session ends two ways: the AI wraps up on its own once the major risks are covered, or you click the lit Planning chip next to the composer at any point. Either way an end card closes the session, and the AI's normal build behavior returns on the next turn.
The wrap-up
A session ends with a plain-language summary in the chat: the decisions you confirmed and the risks you chose to accept, each named specifically. Nothing to export or re-paste — when you then ask OrgBolt to build the change, the build turn reads the wrap-up straight from the conversation.
The Review skill
Skills are a family, and /review is the second one: a one-shot audit of the task's saved artifacts before you deploy. It checks the artifacts against what you asked for, field-level security coverage, deploy order, and anything a new rule might do to existing records. It always runs on the Smarter AI level, whatever the task's setting.
The “Review with Smartest AI, then deploy” button and typing /review do the same thing.
What it costs
Planning turns are ordinary turns: they debit credits by what they actually cost, shown per turn in the chat. A typical session runs a handful of short turns. There's no separate charge for starting or ending a session.