| name | ppt-source-planner |
| description | Use when analyzing research materials and user requirements to produce a source audit, slide outline, and visual style plan before any PowerPoint slide production begins. |
PPT Source Planner
Purpose
Turn source materials and the user's request into an approved factual plan for a presentation. This skill stops before image generation or PPT construction.
Inputs
- user request, audience, language, tone, page count, and delivery context
- papers, PDFs, images, charts, notes, datasets, code results, or screenshots
- any existing template, style requirement, or previous deck constraint
Required Outputs
Write these files in the deck delivery folder:
source_audit.mdslide_plan.mdstoryboard/visual_style_spec.md
Source Audit Rules
source_audit.md must include:
- task type, audience, requested language, page count target, and meeting/report scenario
- all source files read and their roles
- core problem, method, contributions, experiments, results, limitations, and conclusion
- important numbers, units, metrics, labels, equations, baselines, abbreviations, and claims that may guide slide generation
- figures or tables that should be reused, recreated, cropped, or summarized
- uncertainty list: anything not directly supported by the sources
Do not invent experiments, values, claims, citations, or terminology.
Slide Plan Rules
slide_plan.md must list every planned slide with:
- slide number
- proposed title or topic
- purpose in the talk
- one core message
- supporting source evidence
- visual type
- required assets
- expected editable objects
- allowed external-source raster exceptions and why
- wording preferences or allowed acronyms/proper names when the user specifies them
Visual Style Spec Rules
storyboard/visual_style_spec.md must define:
- aspect ratio and page size
- visual tone and density
- color palette and typography direction
- layout grid and margin rules
- figure/chart treatment
- footer/page number treatment
- any user-specified wording or language preference
Approval Gate
After writing the audit, plan, and style spec, ask the user to approve or revise. Do not create storyboards, slide images, editable PPTX files, previews, or QA files before approval. If the user explicitly delegates approval in advance, such as asking Codex to decide and run through the workflow without stopping, record that delegated approval in slide_plan.md and continue.
