Core · Module 2
Specialist Agents
Course outcome 2Project 1: agent brief
Learn how to write a brief a specialist agent can follow. A good brief covers who the agent is, what it does, its limits, how you’ll know it worked, and what it should never do.
Big idea Professional-first agents can still be warm; process beats banter.
By the end of this module, you’ll be able to:
- Configure a specialist agent profile for a given enablement workflow, with a name, job, constraints, checkable success criteria, and non-goals.
- Apply professional-first guidance when you write the brief’s tone and process rules (clarity and process over banter).
- Revise your brief based on the feedback before you download it (if the check flags anything).
How you’ll show it: Project 1, your agent brief (download). Course outcome 2 of 6
What good looks like
This is the bar each part needs to reach (Meets). You’ll get feedback on each part when you check your work.
- Clarity: a name of at least 2 words and a job that says what the agent does, and for which enablement workflow (drafts, modules, briefs…).
- Constraints: at least one clear limit (only, never, before…) and a tone or process rule, like “professional, plain-language comments”.
- Observable success: something a person could check, like a score, count, checklist, or pass/fail, tied to the drafts or outcomes.
- Non-goals: at least one specific thing the agent won’t do, like “does not publish quizzes”.
How you pass: all four parts at Meets or better. If the check flags something, revise that part and check again.
The automatic check looks for a few signals of these. It can’t judge quality, so aim for the description, not the keywords.
Fast-track
Your Fast-track summary
A strong agent brief has four parts that each need to meet the bar:
- Clarity: a name of 2+ words and a job of 40+ characters, with an action verb and what it works on.
- Constraints: a clear limit plus a tone or process rule, like “professional tone”.
- Observable success: something you can check, like a score, checklist, or pass.
- Non-goals: what it won’t do, phrased as “does not”, “never”, or “out of scope”.
Exceeds is bonus polish and never required.
Note: On Fast-track you can skip the lesson, but the agent brief project below is still required (about 10 minutes). It’s how you show Course outcome 2. M3 is still required too.
Anatomy of an agent brief
An agent follows its brief literally. Vague words give it nothing to act on, and missing limits let it wander into work you didn’t ask for.
| Vague | Observable |
|---|---|
| “Makes good briefs.” | “Every brief passes the 5-item review checklist.” |
| “Reviews drafts as needed.” | “Reviews each new module draft before SME sign-off.” |
| “Keeps things professional.” | “Comments in plain language; no jokes or emoji.” |
Why non-goals matter: they set the blast radius. An agent told it “does not edit the source files” can’t accidentally overwrite a course. Without that line, it might.
Your scenario: Set up a specialist agent that reviews new enablement module drafts. It checks that outcomes and evidence line up before the subject-matter expert (SME) signs off.
See a strong example (for a different agent)
This example is for a different job, so you can see the pattern without copying it. Notice what makes each part work.
- Name
- Quiz Item Writer Two words that say what it does.
- Job
- Drafts five scenario-based quiz items for each new enablement module, matched to the module’s stated outcomes. Action verb, what it works on, and the output.
- Constraints
- Only uses content from the approved module draft. Plain language, no trick questions. A clear limit (“only”) plus a tone rule.
- Observable success criteria
- Each module gets 5 items; every item maps to one outcome and passes the item-review checklist. A number and a checklist someone could verify.
- Non-goals
- Does not publish quizzes, grade learners, or change module content. Boundaries phrased as “does not”.
Weak version, for contrast: “Helper Bot · helps with courses · be nice · looks good · n/a.” Nothing here can be checked, and there are no boundaries.
Your project: write your agent brief
Fill in each part, rate yourself, then check it. If anything needs a tweak, you’ll get specific tips.
Tip: Feedback is automatic. It looks for specific details, like a number, a named owner, or a “when”. It’s a quick check, not a grade.
Your feedback
How to read this: Meets = good to go. Emerging = needs a tweak. Exceeds = bonus polish, never required.