PRODUCTIVITY

Research-to-PPT deck and design concept

Research a topic with verifiable evidence, then create the presentation strategy, slide storyboard, design system, and visual production brief.

PROMPT
Role: a precise operations analyst

Objective: Research, structure, and art-direct a persuasive presentation whose claims, narrative, and visual system are ready for slide production.

Inputs:
- Presentation topic: {{presentation_topic}}
- Presentation goal and desired action: {{presentation_goal}}
- Audience: {{audience}}
- Design direction and brand rules: {{design_direction}}

Workflow:
1. Define the presentation objective, audience knowledge, desired post-talk action, and delivery setting.
2. Use the execution date as the research cutoff and collect material claims and figures from official primary sources into a source ledger.
3. Build a story arc around one governing message and three to five supporting arguments, including objections, risk, and next action.
4. Unless the content requires otherwise, target roughly 10–12 slides; give each slide one message, a conclusion-style headline, visual evidence, and separate speaker notes.
5. Specify color, typography, grid, spacing, imagery, icon, and chart rules as design tokens, then art-direct representative slide concepts.
6. Recheck every number and quotation; remove crowded slides, decorative charts, and unsupported claims.

Output format:
## Presentation strategy
## Research plan and source ledger
## Governing message and story arc
## Slide-by-slide storyboard
## Design system and tokens
## Representative slide concepts
## Image and chart production briefs
## Speaker notes
## Final QA

Quality rules:
Use only supplied material and verifiable facts. When information is missing, do not guess: state the gap, any necessary assumption, and its effect on the result. Before concluding, check every constraint and required output field.

Negative prompt

Unsupported facts, fabricated citations, vague conclusions, missing constraints, unverified claims, and unrequested scope expansion

Workflow

  1. Fill variables with concrete facts, scope, actors, and desired outcomes rather than abstract adjectives.
  2. Check the assembled prompt for conflicting conditions, then paste it into a compatible tool.
  3. Treat the first answer as a draft and refine one failed condition at a time.

Verification

  • Confirm every goal, constraint, and output field is present.
  • Check figures, dates, quotations, and code against primary sources and real tests.
  • Keep a human responsible for evidence, feasibility, and final approval.