Skip to content

For the complete documentation index, see llms.txt. Markdown versions are available by appending .md to documentation page URLs. Read the agent handbook.

Zortex Docs
Start searching Install Vision
Write a useful task brief

Write a useful task brief

Describe the outcome, scope, and completion evidence without having to prescribe every tool call.

On this page

A useful task brief tells the agent what result you need and which constraints change the work. You do not need to provide internal IDs or a sequence of tool names when the agent can discover them.

Start with an observable outcome

Vague request More useful request
Look at my files. Find the current website-redesign decision and cite its supporting source.
Work on the document. Replace the outdated pricing paragraph in the selected document and show the saved change.
Check the browser. Open the specified public page, read the main heading, and return the URL and heading.
Fix the project. Reproduce the reported setup failure, repair its cause, and verify the same setup path.

The result should make it possible to tell whether the work is finished.

Include only constraints that matter

Specify an account, project, period, destination, format, or exclusion when it affects the result. Preserve choices already established in the conversation; the agent should not ask you to repeat them routinely.

For research:

Summarize the launch decisions from the named project sources for the last planning period. Separate confirmed decisions from proposals. Cite each material point and do not change the original records.

For an app change:

Update the selected project document with the three approved milestones. Preserve the rest of the document. Read back the changed section and give me the document link.

For a file:

Export the selected report as a PDF in the agreed output folder. Check that the revised heading and final chart appear correctly, then return the actual file.

These briefs specify useful results. The agent still needs to inspect the current target and the available capability before acting.

Let the agent recover routine detail

The agent should inspect available sources, existing context, and the target's current state. It should choose between stored information, live app operations, browser interaction, and computer tools according to the task.

If two different accounts or documents remain plausible and that choice changes the action, a focused question is useful. A request to enumerate every connected app is unnecessary when the installed inventory can answer it.

For requests involving several stages, ask for a short plan that names outputs and dependencies, then continues into execution. A plan alone is not the completed task when you asked for action.

Define the delivery stage

State the stage when it changes the scope: draft a message, save a document, create a local patch, merge a change, deploy a site, or publish a package. These are different results.

A handbook-only request can finish with the updated canonical documentation. It does not automatically expand into implementing every documented behavior or releasing a new product version.

For later or recurring work, the agent must use scheduling capabilities actually available in its host. Indra's connection and sync jobs are not a general scheduler for arbitrary user tasks.

Correct the task while it runs

You can change a constraint or narrow the scope. Tell the agent which part changes; it should preserve valid completed work and identify which earlier changes need updating. If you want work stopped, say so explicitly and check any separately running operation using Follow long-running work.

Finish by checking the requested output and its evidence. Review and deliver results gives practical completion checks.

Suggested