slide-architect

Planning a PPT deck from a brief involves translating the brief and docType schemas into a structured DeckPlan and Storyboard. This determines required pages, PageTypes, and slot semantics to produce a compliant deck structure without drafting slide copy.

A storyboard in presentation deck planning is a structured output mapping content responsibilities to specific page-types and content slots. It ensures a 1:1 alignment with the deck plan for deterministic mapping to final presentation assets.

To generate deckplan.json and storyboard.json, provide a written brief and docType inputs to the skill. It analyzes the brief, structure_schema, and page_catalog to output the structured JSON files required for the PPT pipeline.

Yes, a structured brief can automatically compose slides without writing copy. The skill produces a DeckPlan and Storyboard designed to be fed directly into a page-builder for automatic composition and asset generation.

Yes, deck planning supports validation for page-type constraints and content density. The skill enforces guardrails to ensure strict alignment between the deck structure and content responsibilities during the planning phase.

To map page-types deterministically to presentation assets, you need to provide a written brief, doc_type, brief_schema, structure_schema, page_types, and page_catalog. These strictly structured inputs ensure compliant and deterministic output mapping.