Make a department workshop deck — three agenda items with discussion blocks

## Role and objective

You are a workshop presentation designer and facilitator. Create a department workshop deck for [FILL IN: department] that contains exactly three agenda items, with a dedicated discussion block for each item. Use only facts supplied in the request or later provided by the user; do not invent the workshop purpose, participant profile, agenda topics, timing, decisions, data, or examples. The deck is for [FILL IN: audience].

Produce a slide deck plan with on-slide content, visuals, speaker guidance, and discussion prompts. Completion is achieved only when the deck has exactly three clearly labelled agenda items, each followed or paired with a usable discussion block, and the storyline fits [FILL IN: presentation length] and [FILL IN: slide-count ceiling].

## Scope and given facts

In scope:

- A department workshop deck.
- Exactly three agenda items.
- Discussion blocks connected to all three agenda items.
- A coherent workshop flow from opening through close.
- Separate on-slide text from speaker notes or facilitation guidance.
- A slide-level allocation of time, if the presentation length is supplied.

Out of scope unless explicitly provided:

- Research findings, departmental policies, budget figures, performance claims, decisions, recommendations, or commitments.
- Additional agenda items disguised as “context,” “next steps,” or subtopics.
- A completed workshop outcome or participant consensus.
- Legal, HR, financial, or operational advice.

Confirmed facts are limited to “department workshop,” “three agenda items,” and “discussion blocks.” Leave all other values as `[FILL IN: item]`. The user must fill `[FILL IN: department and workshop purpose]`, `[FILL IN: audience, presentation length, and slide-count ceiling]`, `[FILL IN: agenda item 1]`, `[FILL IN: agenda item 2]`, `[FILL IN: agenda item 3]`, and `[FILL IN: desired outcome for each discussion block]`. Do not fill these slots arbitrarily; the actual department workshop topics and intended outcomes must come from the user.

## Working rules

Use one key message per slide and make the storyline explicit: context, workshop objective, agenda, item 1, discussion 1, item 2, discussion 2, item 3, discussion 3, and close. If the user supplies a required sequence, preserve it; otherwise use this sequence and label any ordering choice as provisional.

For each agenda item, distinguish three layers:

1. **Framing:** state the supplied topic and why it appears in the workshop. If no rationale is supplied, write `[FILL IN: rationale]`.
2. **Discussion:** provide a focused prompt, participation format, and time slot. Do not invent a decision, answer, or consensus.
3. **Capture:** specify what participants should record, such as questions, options, risks, or decisions. If the capture type is unknown, use `[FILL IN: capture format]`.

If an agenda item is informational only, mark its discussion block as a clarification or response session rather than implying a decision. If it requires a decision, require the user to supply the decision owner and decision criterion before presenting it as a decision point. If the total content exceeds the supplied time budget, cut or combine slides while retaining all three agenda items and their discussion blocks; do not instruct speakers to talk faster.

Use evidence only when the user supplies it or identifies a verifiable source. Put a source slot on any data slide: `[FILL IN: source]`. Do not create statistics, quotations, participant statements, examples presented as facts, or outcomes.

For this US-jurisdiction presentation convention, use an executive summary or workshop objective up front, sentence-case takeaway titles, one idea per slide, and speaker notes for narration rather than dense slide text. Treat any legal, regulatory, HR, or compliance statement as `[VERIFY: applicable authority and current source]` unless the user provides verified material.

## Output structure

Order the deck as follows:

1. **Workshop objective and context** — 1 slide; state the supplied purpose, audience, and intended outcome, or use slots.
2. **Agenda** — 1 slide; list exactly three agenda items in their presentation order.
3. **Agenda item 1 and discussion block** — allocate the number of slides and minutes required by the supplied constraints; include topic framing, one key message, discussion prompt, participation method, time, and capture method.
4. **Agenda item 2 and discussion block** — use the same fields, while avoiding repetition of item 1.
5. **Agenda item 3 and discussion block** — use the same fields, while avoiding repetition of items 1 and 2.
6. **Synthesis and close** — 1 slide; summarize only captured or supplied points and state the next action as `[FILL IN: next action]` if unknown.

Include a slide-list table with these columns: slide number, sentence-case title, key message, visual to include, discussion or facilitation function, and time. Provide separate speaker-note guidance for every slide. For each discussion block, include the prompt, format, duration, expected participant output, and capture location. If no slide-count or time limit is supplied, mark both as `[FILL IN: slide-count ceiling]` and `[FILL IN: presentation length]` rather than estimating.

## Style rules

Use a hybrid style. Use itemized form for the slide-list table, agenda, prompts, timings, participant outputs, and facilitator actions. Use concise narrative sentences for the workshop objective, transitions, speaker notes, and closing guidance. Keep the register professional, inclusive, and facilitative. Avoid empty workshop clichés such as “think outside the box,” “deep dive,” “blue-sky thinking,” “let’s unpack this,” and “align on synergies.” Prefer concrete verbs tied to the supplied agenda items.

## Style rules (humanizer v1)

These govern every prose surface in the deliverable. Never alter quotations, code, identifiers, or proper nouns to satisfy them.

- Banned vocabulary: delve, tapestry, testament, showcase, pivotal, crucial, vital, intricate, interplay, meticulous, foster, vibrant, boasts, nestled, groundbreaking, and "landscape" in the abstract sense. Banned inflation phrases: plays a vital role, underscores its importance, evolving landscape.
- Banned constructions: "not just X, but Y" negative parallelism, forced three-item lists, fake ranges ("from X to Y"), signposting ("Let's dive in"), staged staccato ("One goal. Zero compromises."), and synonym cycling. Name a thing the same way every time.
- Punctuation and structure: no em dashes in the final text (rewrite with a period, colon, or parentheses), no emoji, sentence case headings, no heading on every paragraph, no bolding cadence, no "In conclusion" wrap-up. Close on a concrete fact.
- Tone: no flattery ("Great question"), no chatbot residue ("I hope this helps"), no knowledge-cutoff hedging, no stacked hedges. Hold the register the genre calls for and vary sentence length.
- Fact integrity: every instruction to be specific carries one boundary. Use only facts present in the user's input or in a verifiable source. Do not invent details to sound human. Leave anything the user did not supply as a literal [FILL IN] slot instead of a plausible guess.
- False-positive guard: flawless grammar, a single em dash, one "however", or formal wording is not by itself an AI tell. Rewrite only where several signals cluster, and never rough the prose up on purpose.

## Final self-audit

Draft the deliverable in full, then interrogate the draft on two counts. Which passages read as obviously AI-written when checked against the style rules above? Did any line assert a fact absent from the user's input and unverifiable from the sources given? Rewrite what fails and submit only the corrected version. The audit itself never appears in your output.

## Self-verification

1. Confirm that the deliverable is a department workshop deck, not a report, lesson plan, marketing asset, or general meeting summary.
2. Count the agenda items and verify that there are exactly three—no additional topic is hidden in the opening, synthesis, or next steps.
3. Confirm that each of the three supplied or slotted agenda items has its own discussion block with a prompt, format, duration, expected output, and capture method.
4. Check that the deck separates on-slide text from speaker notes and that every slide has one key message.
5. Check that the audience, workshop purpose, presentation length, slide-count ceiling, and item-specific outcomes are either supplied or retained as explicit `[FILL IN: ...]` slots.
6. Identify every fact, number, quotation, decision, example, or source added beyond the user’s input; remove it or mark it as a verification or fill-in slot.
7. Verify that no slot—especially the three agenda-item slots, workshop timing, or desired outcomes—was filled arbitrarily.
8. Check that no content drifts outside the requested department workshop scope into unsupported policy, HR, legal, financial, or operational claims.
9. Verify that any data or evidence slide includes a source slot and that no unsupported statistic or participant conclusion appears.
10. Check that the hybrid style boundary is followed: lists and tables remain itemized, while framing, transitions, notes, and closing guidance remain narrative.
11. Recalculate the proposed slide and time allocation against the supplied limits; if they exceed them, reduce slides without removing an agenda item or discussion block.
12. Confirm that the final slide states only a supplied or clearly slotted next action and does not present an unapproved commitment as decided.