skills/create-professional-presentation/references/workflow.md

# Creation workflow

## Intake

Extract objective, audience, expected result, scope, duration/slide constraint, consumption mode, sources, template/brand, language, confidentiality, accessibility, notes/citations and final formats. Mark each as explicit, delegated, inferred, absent/ambiguous or N/A.

## Mandatory requirements confirmation

Before web research, production storyboard, slide code or file generation, present a compact requirement table with: requirement, proposed value, state and rationale when inferred. Always include the two research options:

1. `FILES_AND_CONTEXT_ONLY`: use only current knowledge/context and attached files; no web.
2. `WEB_COMPLEMENTARY`: complement with verified web research after confirmation.

Ask the user to confirm the complete brief or provide adjustments. Stop in `PENDING_CONFIRMATION`. Continue only after an explicit confirmation; incorporate adjustments and obtain confirmation of the revised brief. A material later change requires reconfirmation.

## Route and analyze

After confirmation, apply the minimum sufficient materiality level. Build a claim ledger when evidence is material. Browse only when `WEB_COMPLEMENTARY` is confirmed; never browse with `FILES_AND_CONTEXT_ONLY`. For M3/M4 or high criticality, perform the adversarial pass before writing conclusions and compose an installed H.AMA capability when available.

## Architect

Choose a narrative family, define the central message and create a storyboard. Each slide needs function, message, evidence, representation and acceptance criterion. Verify the horizontal title sequence.

## Design and build

Select representations by question, not fashion. Use Presentations with `@oai/artifact-tool` and native/editable objects for information. Respect brand/template and accessibility. Keep slide count exact. Never route production to Gamma, Presenton or another external generator.

## Validate and deliver

Run integrated assurance. If producing a file, render every slide, inspect, fix and rerender. Deliver one final version per product; mention only limitations that affect use.