Write a clear task - AgentDesk Docs

Start in ordinary language. A Product Owner or suitable agent can help turn an idea into a brief; you do not need to write every detail before asking.

Include the information that changes execution

Part	What it explains
Title and goal	The outcome you want.
Context	Why the work matters and which project, source, or earlier decision applies.
Scope	What is included.
Out of scope	Changes the executor should avoid.
Expected output	The document, application, analysis, code change, or other result.
Acceptance criteria	Observable conditions for success.
Verification	How each important condition will be checked.
Responsibility	Owner and intended assignee.
Dependencies and next action	What must happen first and what happens next.

Example brief

Title: Create a customer onboarding guide

Goal: Help new customers complete their first project without assistance.

Context: Use the attached current UI screenshots and product notes.

Scope:
- Explain sign-in, project creation, first task, and output review.
- Include examples and links to the current product.

Out of scope:
- Product code changes.
- Sending the guide to customers.

Output:
- HTML guide and downloadable PDF in this task's Deliveries.

Acceptance:
- Every step matches the current UI.
- Links resolve.
- PDF is readable on A4 with no clipped text.
- Review proof identifies the source screenshots and checked files.

Verification:
- Validate links, render the PDF, and inspect each page.

Next action:
- Draft the guide in Inbox for review before execution approval.

Make criteria testable

“Easy to use” is difficult to verify. Prefer “A new user can locate Add work item, create an Inbox item, and open its Task Detail using the documented steps.” For UI work, identify the behavior and intended environment. For reports, identify source data and method. For documents, identify format, audience, links, and layout checks.

Use the right structure

Use a checklist for checkpoints within the same task. Use a dependency for a prerequisite task. Use a separately assigned child or related task for work that needs its own responsibility and lifecycle. An attachment supplies context; it is not a dependency. A mention in a comment is communication; it is not an assignment.

Approve after review

After the task exists and the brief is adequate, give a later task-specific approval, for example:

I approve TASK-ID's scope and acceptance criteria.
Assign it to the documentation agent and move it to Ready.

If decisions are still open, keep it in Inbox and say what must be clarified. See Create and review your first task.