ppt-slide-planner

name	ppt-slide-planner
description	Plan precise slide-by-slide PPT structures from a topic, text content, requirements, or uploaded-material summaries, and prepare a file-generator-ready PPTX payload for downstream generation. Use when the user asks for PPT planning, PowerPoint outline, slide planning, page-by-page PPT requirements, presentation storyboard, report deck structure, pitch deck outline, training deck plan, proposal slides, project report slides, business review slides, or when the user asks to first create a precise outline before generating a PPT file. This skill is the planning and layout layer, not the PPTX file generator.
when_to_use	Use this skill when the user wants a PowerPoint/PPTX deck planned from a topic, notes, copied text, summarized source material, or agent-prepared outline; use it for presentation planning, slide-by-slide content design, page splitting, layout selection, brand styling, media placeholder planning, and preparing structured requirements for the file-generator skill.
runtime_type	prompt
max_calls_per_turn	5
timeout_seconds	60
display	{"icon":"presentation","category":"content_creation","scenarios":["content_creation","office_collaboration","business_operations"],"label":{"en_US":"PPT Slide Planner","zh_Hans":"PPT 规划器"},"description":{"en_US":"Designed for reports, proposals, training, and presentation decks; plans each slide's purpose, content, layout, visual style, and media placeholders before PPTX generation.","zh_Hans":"适用于汇报、方案、培训或演示文稿制作，可在生成 PPTX 前逐页规划目标、内容、版式、视觉风格和媒体占位。"},"when_to_use":{"en_US":"Use when PPT content must be planned page by page before file generation.","zh_Hans":"当需要先逐页规划 PPT 内容和排版，再生成文件时使用。"},"tags":{"en_US":["PPT","Presentation","Slides"],"zh_Hans":["PPT","PPT规划","幻灯片编排"]}}

PPT Slide Planner Skill

Use this skill to turn a user's topic, text content, requirements, or source-material summary into a strict per-slide construction plan. This skill plans the PPT only; the actual editable PPTX file is produced by the separate file-generator skill.

This skill must not call PPTX generation tools, render PPTX files by itself, implement fallback renderers, or bypass file-generator. When the user asks for a PPT file, first produce the planning output and then route that output to the file-generator skill, which owns generate_pptx.

Workflow

1. Determine whether the user provided enough context: topic, audience, use case, slide count or duration, style or brand requirements, and source content.
2. If the topic, source content, audience, or use case is too unclear to produce a reliable deck, call request_user_input before planning. For slide count, style, and layout preferences, make conservative defaults when the content is otherwise clear and state the assumptions.
3. Read deck-brief.md and produce a concise internal deck brief.
4. Read slide-plan-contract.md and create a slide-by-slide plan. Every slide must have exact title text, body text, page objective, layout, element list, and media placeholder requirements.
5. Read slide-layout-contract.md and select a concrete layout for each slide.
6. Read media-placeholder-contract.md when the deck needs image, chart, diagram, or video placeholder areas.
7. Read pptx-payload-contract.md and convert the slide plan into one complete strict JSON object that can be passed later as file-generator/generate_pptx.presentation.
8. Read quality-check.md and self-check every slide before handoff. If any text element may overflow, increase h, reduce text, add line breaks, or split the content before preparing the payload.
9. Before handoff, verify presentation starts with {, ends with }, contains only strict JSON, has balanced braces/brackets, closes the slides array, and contains no Markdown fences, comments, prose, trailing commas, or unquoted visible text.
10. Return or hand off the strict slide plan and PPTX payload to the file-generator skill when file output is required. Do not call generate_pptx from this skill.
11. In the final answer, briefly mention that the PPT plan is ready for file generation and list any important assumptions. Do not paste the full presentation JSON unless the user explicitly asks for it.