# Demo prompts — Chapter 4.2

Two ways to drive the demo. Pick one for the recording.

---

## Option A — using the `research-brief` skill (recommended)

This is the cleaner demo, and it's a perfect callback to Section 2.3 — viewers watch the skill they learned to build, doing real work.

**Setup before recording:**
1. Install `skills/research-brief/SKILL.md` into Cowork (Settings → Skills → Add).
2. Confirm `brief-template.md` is in the connected working folder.

**Paste this into Cowork:**

```
Draft me a brief: should we switch our team CRM from HubSpot to Attio in Q1 2026?
```

That's it. The skill enforces every rule — plan-before-action, cite-as-you-go, structure first, take a real position, save the output to a file. You just narrate what's happening.

---

## Option B — bare prompt (fallback if the skill isn't installed)

For students who haven't built their skills folder yet, or for showing what the skill is *doing under the hood*.

```
Help me decide: Should we switch our team CRM from HubSpot to Attio in Q1 2026?

Use the structure in brief-template.md — fill out every section.

Rules:
- Cite every claim inline with a link or source name.
- Verify pricing, integration counts, and any other specific numbers before stating them — open the actual pricing pages.
- For the Compare table, set the criteria yourself based on what matters for a small team CRM switch. Suggested starting points: price per seat, integrations, migration effort, support, AI features, mobile experience.
- Mark anything uncertain with a "?".
- Take a real position in the Recommendation. If it depends, say what it depends on, then take the position anyway under your best assumption.
- Keep the body under 800 words.

Before researching, show me the sharpened question, the Compare criteria, sources you'd prioritize, and rough timing. I'll approve or adjust.
```

---

## Notes for the recording

- **Use Option A.** It demonstrates the whole arc of the course — Section 2 taught them to build a skill, Section 4 shows the skill paying off.
- Swap the question for any real decision you're weighing — works just as well for "switch from Notion to Confluence," "hire a fractional CTO vs full-time senior engineer," etc.
- After Cowork shows its plan, *change one thing* on camera (drop a criterion, push back on the timing, add a source). Shows the approval step is real.
- Don't paraphrase the rules section live (if you go Option B). Read it or paste it — viewers should see the *literal* prompt because the precision *is* the lesson.