editable-ppt-orchestrator

name

editable-ppt-orchestrator

description

Must be the first skill used when the user wants to create, generate, design, or improve a high-quality editable PPT/PPTX/slides/deck/presentation from requirements, PDFs, papers, images, charts, screenshots, notes, source code, research materials, or folders. Trigger on 做PPT, 生成PPT, 汇报PPT, 组会PPT, 论文PPT, 答辩PPT, presentation, slides, seminar, journal club, defense, conference talk. Run this before Presentations, PowerPoint, or artifact-tool authoring. Orchestrates source audit, slide plan, full-deck imagegen storyboard generation, storyboard contact-sheet review and freeze, element-level image-to-editable PPT conversion, true rendered previews, object audits, independent workflow/visual/content review gates, and packaged delivery.

Editable PPT Orchestrator

Role

This skill is the lead controller for strict editable PowerPoint production. It decides sequence, delegates each concrete step to the specialist skills, enforces stage gates, and keeps every artifact in one delivery folder.

It does not replace imagegen, image-to-editable-ppt, Presentations, or the specialist PPT skills. It coordinates them.

Invocation priority: for high-quality editable deck creation from user materials, this skill must run before any direct Presentations, PowerPoint, artifact-tool, JSX deck authoring, or direct PPT authoring workflow. Do not load or follow those authoring workflows before the source audit, slide plan, imagegen storyboard, and image-to-editable conversion path have been established.

Presentations, PowerPoint tooling, LibreOffice, or artifact-tool based rendering are allowed only for post-conversion rendering, inspection, final merge, export, and QA evidence. They must not replace imagegen storyboarding or image-to-editable conversion.

Storyboard rule: imagegen must produce the complete final-content slide images for the whole approved deck before editable conversion starts. The AI should first understand the user request and source materials, then let imagegen produce a coherent near-final storyboard set with its own content organization, visual hierarchy, style, diagrams, figures, labels, captions, and layout. Review the full storyboard set as a contact sheet, then freeze it. Editable conversion uses the frozen imagegen storyboards as the source images and converts them into element-level editable PPT objects; it compares against the imagegen storyboard, not the source/spec, and must not add missing content that was absent from the storyboard.

Element-level conversion rule: when the accepted storyboard is an imagegen slide, do not approximate-redraw or substitute generic icons. Rebuild only ordinary text, numbers, simple straight lines, and simple boxes/rounded boxes as native PPT objects. Crop everything else as independent complete picture objects: stylized icons, badges, styled arrows, charts, tables, plots, diagrams, complex panels, figures, logos, screenshots, and decorative visual elements. Track picture crops in a human-auditable inventory with meaningful asset names, source_bbox, display_bbox, role, and padding/cleanup notes. Avoid turning the slide into hundreds of generic fragments. Crops must not be clipped or unintentionally overlap neighboring content. Each converted slide must pass rendered QA before the next conversion slide starts.

Freeze rule: after storyboard/storyboard_freeze.md is written, do not call imagegen again during editable conversion. If conversion quality is poor, fix bbox, source_bbox, crop padding, text boxes, z-order, object splitting, or the conversion manifest. Re-enter imagegen only before storyboard freeze, or after explicit user approval to unfreeze and replace the affected storyboard image.

Core rule: the lead orchestrator produces and fixes; independent reviewers approve. The lead orchestrator must not self-approve a slide or final deck.

Do not read, inherit, reference, or mix in presentation-template-workflow unless the user explicitly asks for that exact skill. This skill is an independent workflow.

Read First

Load only the reference files needed for the current stage:

• references/boundary.md: skill boundaries, specialist ownership, and reviewer authorization rules.
• references/workflow-blueprint.md: required stage order, full-deck storyboard batch, conversion loop, page gate states, and final assembly.
• references/artifact-contract.md: required folder structure, required artifacts, editability rules, and raster exceptions.
• references/review-gates.md: storyboard, visual, content, and final review checks.

Specialist Skill Map

Use these child skills as the concrete implementation steps:

• ppt-source-planner: source audit, slide plan, and visual style spec before user approval.
• ppt-imagegen-storyboard: imagegen-based complete storyboard for one slide.
• ppt-storyboard-reviewer: independent review of storyboard completeness, source alignment, readability, and readiness.
• ppt-image-to-editable-converter: element-level conversion of a frozen storyboard into segmented PPT objects with manifest, preview, and object audit.
• ppt-deck-qa-gate: independent workflow audit, visual/content QA, page gates, and final deck gates.

Required Flow

Follow this order exactly:

source materials + user request
-> source audit
-> slide plan + visual style spec
-> user approval
-> full-deck imagegen storyboard batch
-> storyboard contact-sheet review and freeze
-> slide-by-slide editable conversion loop
-> final assembly
-> final deck review

Do not start slide production until the user has approved the outline, page count, content direction, and visual style.

Generate the full storyboard set before starting editable conversion. During conversion, finish the full page gate for the current slide before converting the next slide.

Reviewer Rule

If the user explicitly authorizes multi-agent review, spawn or call independent reviewer agents for storyboard, workflow/process audit, visual fidelity, content QA, and final deck QA. Their review files may approve PASS.

If the user has not authorized multi-agent review, do not claim independent agent review and do not mark gated review files as PASS. Ask the user for authorization or set the affected slide/deck to BLOCKED. A lead self-check may be written as advisory evidence, but it is not a substitute for *_review_by_agent.md.

Workflow Auditor Rule

Use a Workflow Auditor as the global process reviewer. This reviewer checks the sequence, not just slide appearance.

The Workflow Auditor must review the package before any slide is marked PASS and again before final delivery. It verifies:

• editable-ppt-orchestrator was the controlling workflow for the task.
• Presentations, PowerPoint, artifact-tool, JSX authoring, or direct PPT authoring did not run before source audit, slide plan, imagegen storyboard, and element-level image-to-editable conversion were established.
• Presentations/artifact-tool usage, if any, was limited to rendering previews, inspecting, final merging, exporting, or QA evidence after editable conversion.
• The deck followed the required order: slide specs -> full-deck imagegen storyboard batch -> storyboard contact sheet -> storyboard review -> storyboard freeze -> element-level image-to-editable conversion -> true render -> object audit -> independent visual/content reviews -> PASS.
• No editable conversion started before the full storyboard set was reviewed and frozen.
• The next conversion slide did not start before the current converted slide reached PASS.
• No imagegen call occurred after storyboard freeze unless the user explicitly approved unfreezing and replacing a storyboard image.
• Review files were produced by independent reviewers when multi-agent review was authorized.

Required outputs:

• qa/workflow_audit_by_agent.md before any slide PASS, or qa/workflow_audit.md only when agents are unavailable and the user accepts non-agent review.
• qa/final_workflow_audit_by_agent.md before final delivery, or qa/final_workflow_audit.md only when agents are unavailable and the user accepts non-agent review.

If the Workflow Auditor returns FAIL or BLOCKED, fix the process violation or return to the correct stage before continuing.

Delivery Folder

Create one delivery folder and keep all generated files inside it:

source/
assets/
slide_specs/
storyboard/
manifests/
editable_slides/
previews/
qa/
final/
scripts/

See references/artifact-contract.md for required files and naming.

Hard Anti-Patterns

• Generating slide images before user-approved outline and style.
• Starting editable conversion before all planned storyboard images, the storyboard contact sheet, and storyboard freeze file exist.
• Loading or following Presentations, PowerPoint, artifact-tool, or JSX deck authoring before imagegen storyboard and image-to-editable conversion are established.
• Marking any slide PASS before the Workflow Auditor confirms the process sequence is valid.
• Treating imagegen output as a loose suggestion after the storyboard is frozen.
• Re-entering imagegen during conversion to fix crop, text, bbox, z-order, or visual fidelity problems without explicit user approval to unfreeze the storyboard.
• Approximate-redrawing or visually substituting the accepted imagegen slide instead of converting it into element-level editable objects.
• Substituting non-imagegen screenshots, HTML exports, blank mockups, or manually drawn placeholders for storyboards.
• Treating imagegen storyboards as no-text skeletons, decorative backgrounds, mood boards, or content placeholders instead of complete slides with readable final visible content.
• Calling imagegen with style-only prompts instead of a saved imagegen prompt trace derived from the slide spec.
• Starting the next conversion slide before the current converted slide reaches PASS.
• Lead self-approving a slide or final deck.
• Accepting object counts as visual QA.
• Passing visual QA without a true PowerPoint, LibreOffice, or Presentations render.
• Letting artifact-tool/Presentations become the visual design controller instead of a render/export/merge/QA tool.
• Using a full-slide screenshot or broad crop as final PPT structure.
• Replacing stylized icons, charts, tables, diagrams, arrows, figures, or decorative visuals with newly drawn approximations when they should be independent complete crops.
• Using hundreds of anonymous tiny crop fragments instead of a human-auditable inventory with named visual assets.
• Rebuilding anything beyond ordinary text, simple lines, and simple boxes unless the user explicitly asks for deeper native editability.
• Delivering without review files, page gate evidence, and final deck gate evidence.