I’m preparing for [MEETING OR SESSION] with [ORGANIZATION].

The audience is:
[ROLE]
[ROLE]
[ROLE]

The goal is:[GOAL]

Use [APPROVED BRIEF OR SOURCE] in [APPROVED SOURCE SYSTEM] as context.

My working assumptions are:

1. [ASSUMPTION]
2. [ASSUMPTION]
3. [ASSUMPTION]

Pressure-test each assumption using the approved brief or source. For each assumption:

Rate its strength.

Cite the supporting evidence and source.

Flag gaps, contradictions, or risks.

Give me one question to validate it.

Rewrite it if the evidence supports a better version.


Then recommend:

One clear session objective.

The most useful demo focus or use case.

One measurable KPI.

The stakeholder concerns I should address.

The decisions I should seek.

Any information I still need before creating customer-facing material.


Do not invent facts. Separate facts, assumptions, and inferences. If a source is missing or permission is unclear, stop and ask me.

Using the approved sources and assumption review, create or update [APPROVED WORKING DOCUMENT]. Add a section or tab called [MEETING STRATEGY].

Include:

1. Meeting objective.

2. Audience and stakeholder concerns.

3. Source-backed evidence and working hypotheses.

4. Decisions to seek.

5. Proposed meeting flow.

6. Demo or use-case storyline.

7. Measures of success.

8. Open questions and risks.

9. Points that need human review.



Keep this as a draft. Do not share, send, publish, or replace source material without my approval. Link factual claims to their sources when possible.

Using [APPROVED PRESENTATION TEMPLATE] and the approved meeting strategy, create a concise [NUMBER]-slide presentation.

Suggested structure:

1. Title and meeting objective.

2. What we heard.

3. Priority workflow or demo.

4. What a controlled pilot could achieve.

5. Next steps and decisions.

Requirements:

Use only approved, source-backed information.

Separate facts from hypotheses.

Follow the template’s existing brand and layout rules.

Cite each metric and customer-specific claim.

Add speaker notes only if [APPROVED VOICE GUIDANCE] is available.

Keep the deck as a draft.


End with a checklist of claims, sources, permissions, design choices, and narrative choices that need human review.

Compare the approved final presentation with the generated draft.

Create a change log that groups the edits by:

Story and sequence.

Factual corrections.

Customer or audience context.

Wording and tone.

Visual hierarchy and brand.

Missing context or evidence.

Content removed for safety, privacy, or relevance.

For each pattern, explain what changed, why it changed, and what reusable instruction would improve the next presentation.

Do not change an existing skill, template, or preference file. Draft any proposed updates for human review.