Write your first task

A good task tells Kollab what to produce, what context to use, and how the result will be judged. The goal is not to write a perfect prompt; the goal is to start a piece of work that can be continued.

Before you send

Check four things:

1. Outcome: say what should exist at the end, such as a report, analysis, plan, table, draft, summary, or file.
2. Context: include background, audience, examples, project links, or uploaded files.
3. Constraints: mention tone, language, format, source limits, length, deadline, or things to avoid.
4. Next action: ask Kollab to draft, compare, extract, rewrite, create a file, or use a connector.

Example task

Instead of “help me research competitors,” write: “Create a competitor research brief for our product team. Compare pricing, target users, onboarding flow, and gaps. Use the uploaded notes first, then search public sources if needed. Return a structured report with a short recommendation section.”

After Kollab responds

Stay in the same task. Ask for a revision, attach another file, request a different format, or ask Kollab to turn the answer into an artifact. If the work belongs to a repeating workflow, move the context into a project by following Set up project context.

Common mistakes

• Asking only a question when you need a deliverable.
• Starting a new task for every edit.
• Uploading a file without telling Kollab which parts matter.
• Asking Kollab to use a tool before the connector is available.

For file-heavy work, read Work with files and artifacts. If the task depends on Notion, GitHub, Figma, Linear, reusable skills, or team channels, confirm the needed connector, skill, or bot configuration before running it.