Available in: Chat, Agent, and Project conversations. Each Plan belongs to its conversation; approval applies to the reviewed revision and does not grant separate Site or external-service permissions.
A Plan is a revisioned document attached to a conversation that explains proposed work. It gives you a place to review the goal, scope, approach, and checks before execution.
Use planning when a task has important choices, multiple stages, or consequences that need agreement. A short, clear request may not need a separate planning step.
Review a useful plan
Look for the decisions that would change your approval:
- The intended result and how success will be checked.
- The resources and external systems involved.
- Proposed changes and any consequential actions.
- Assumptions, dependencies, and unresolved questions.
- Costs or operational effects that influence the approach.
For example, a plan to update a customer portal should distinguish editing the Project, validating the preview, and releasing to a selected Site. Agreement to an approach should not conceal a production change.
Revise and approve
Ask for changes when the scope or approach is wrong. Review the resulting revision rather than relying on approval of an earlier draft. Where execution is bound to Plan approval, that approval applies to the exact reviewed revision and its authorized scope.
A Plan can describe a connection or a production action, but the document itself does not grant the required access. Current permissions and execution controls remain in effect.
Follow the result
Compare completion evidence with the agreed outcome. A finished conversation or an optimistic status message is not a substitute for checking the actual result. If work reveals a material change in scope, revise the plan before treating the old approval as permission for new actions.
Use Preferences to choose planning behavior and Prompts to make the initial request clear.
Example: review a portal change
Ask for a Plan to add a priority field to an intake portal. The proposal should identify the form and record changes, how existing records will behave, and the checks needed in the Project preview. If the task includes production, it should name the intended Site and address data compatibility.
If you decide the change should remain in development, request a revised Plan before approving execution. Open /plan through Composer commands; use Messaging if you need to correct work already in progress.
A weekly checklist saved as a file is an ordinary deliverable. A Plan here is the conversation-owned document used to review an approach; see File system for editable deliverables.