Skip to content

Available in: Chat, Agent, and Project Composers. Use a message for the current task and a Skill for a method worth reusing.

A useful prompt gives Playbooks an outcome, relevant context, and the constraints that affect the work. You do not need to prescribe every implementation step, but the operator needs enough information to distinguish a useful result from a plausible one.

Start with the outcome

Compare “analyze this” with a request that names the decision:

Review the attached customer feedback and identify the three problems we should investigate next. Group repeated observations, cite the source for each finding, and separate evidence from interpretation. Write for a product planning meeting.

That request specifies the input, purpose, evidence standard, and audience without choosing the entire method.

Add the details that change the work

DetailExample
AudienceA small operations team with no engineering background
BoundariesDraft the response for review before sending it
ConstraintsUse the supplied material and identify missing evidence
OutputA comparison table followed by a recommendation
SuccessA reader can choose the next action from the result

Attach task inputs as Sources. Use Instructions, Skills, and Files for guidance and background worth retaining across tasks.

Refine in conversation

Point to the part that needs to change and explain the intended effect. “Make the recommendation easier to compare by adding cost and setup columns” provides more direction than “make it better.”

Contextual composer suggestions insert editable text for you to review. They do not submit a task or grant capabilities. Save a reusable method as a Skill when it should inform future tasks.

Use Queue or steer to deliver a correction during active work, or Edit and resend when the original request needs revision.