Your First Task

Now that Chief is installed, give it real work. Chief responds best to specific outcomes, not vague questions.

Example: Sales Summary in #sales

DM Chief or post in any channel where Chief is a member:

Hey Chief, summarize our latest sales data and post it in #sales.

Chief will:

1. Acknowledge with a 👀 reaction.
2. Ask a clarifying question if it doesn’t know where your sales data lives (e.g., “Should I pull from your Stripe integration, or do you have a sheet?”).
3. Run the work — fetching data, summarizing, formatting.
4. Post the result in #sales and link to it from your DM.

The whole loop is usually 30 seconds to a couple of minutes depending on data size.

What Makes a Good First Task

Pick something bounded and verifiable — you’ll be more confident with Chief once you’ve watched it complete a small loop end-to-end.

Good examples:

• Summarize the last 7 days of #engineering and post the highlights in our team channel.
• Take this PDF and pull out every dollar amount mentioned, then make me a quick summary.
• Draft a polite follow-up email to the client thread I just sent — keep it under 100 words.
• What’s the weather in San Francisco tomorrow? Just give me the answer, don’t post anywhere.

Avoid for the first task:

• Anything that touches production systems (Chief can do this, but you’ll want to set up Approval Workflows first).
• Open-ended research with no end state. Chief will do it, but you’ll get better results with concrete asks.

How Chief Reports Status

Chief uses emoji reactions on your message to tell you where it is:

You can interrupt at any time with “Chief, stop” or /chief-stop.

Next: Browse Features

Now that you’ve shipped your first task, see Features for the full list of what Chief can do.