Create an editable HTML presentation with a 16:9 canvas, previous/next buttons, arrow-key navigation, a slide counter and a one-slide-per-page print layout for [PROJECT] and [AUDIENCE]. The task is: Project Kickoff Deck.

## Required content and structure

Cover purpose, scope, roles, milestones, dependencies and immediate next steps.

Use [APPROVED_CONTENT] as the source of names, dates, figures, claims and destinations. List missing inputs before substituting anything. If a demonstration is needed, label its content as fictional. Do not invent customer quotes, rankings, partner logos or product capabilities.

## Design direction

Use [BRAND_RULES] and the design system already selected in the project. If no system is supplied, start with this direction: white, midnight navy and restrained blue; strong alignment and simple evidence diagrams. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.

## Content preparation

Collect the project purpose, scope, decision owners, milestones, dependencies and immediate actions. Identify unresolved responsibilities and dates before writing the narrative.

## Layout and behavior

Move from why the project exists to what will be delivered, who decides and how work begins. Keep the timeline connected to actual dependencies rather than presenting dates as decoration.

## Task-specific acceptance check

- Make unresolved ownership and dates visible.
- Ask whether each participant can identify their next action and decision path.
- Mark proposed owners and dates clearly so the deck does not turn an open discussion into a recorded commitment.

## Implementation and review

Keep text editable. Use semantic structure, descriptive controls, visible keyboard focus and appropriate empty/error states. Check narrow and wide layouts. Respect reduced-motion preferences. Preserve any existing project framework and dependencies; do not silently replace the stack. Return the editable files and explain any incomplete behavior or unsupported inputs. Review this specific task before proposing extra features.

Keep one main idea per slide. Use charts only when actual comparable values are supplied; include units, source dates and limitations. Keep speaker notes separate from visible slide content.

## Reference attachment and reconstruction goal

Attach reference.webp from this prompt’s download bundle alongside this prompt in OpenDesign. Build an editable result with a similar composition and hierarchy; do not embed the whole reference image as the finished interface. Preserve approved project content and brand rules if they conflict with fictional sample labels. If the image is missing or unreadable, ask for it instead of claiming visual fidelity.

## Reference composition and content

Use the attached reference.webp as the visual reference for Project Kickoff Deck. Before building, identify the major regions from top to bottom, their relative widths and heights, alignment, spacing, typography hierarchy, surface colors, borders, imagery and repeated components. Preserve those relationships rather than substituting a generic template. Required task content: Cover purpose, scope, roles, milestones, dependencies and immediate next steps. Use the following task-specific layout guidance when translating the image into editable elements: Move from why the project exists to what will be delivered, who decides and how work begins. Keep the timeline connected to actual dependencies rather than presenting dates as decoration.

## Visual direction from the example brief

white, midnight navy and restrained blue; strong alignment and simple evidence diagrams.

## Slide structure and presentation behavior

Recreate the slide composition as editable title, body, visual and annotation elements. A pictured slide is one view, not evidence of a complete deck. Use the supplied narrative to build any requested additional slides; preserve its typography, margins, color roles and alignment. Move from why the project exists to what will be delivered, who decides and how work begins. Keep the timeline connected to actual dependencies rather than presenting dates as decoration. Keep navigation outside exported slide content. Make unresolved ownership and dates visible.

## Visual comparison and delivery

1. Compare the result with the attached image at matching proportions. Review major region placement, relative image sizes, line breaks, spacing, typography hierarchy, contrast, active states and content density before polishing decorative details.
2. Then test the narrow layout without squeezing desktop text into tiny labels.
3. Keep logos, photos and icons as separate assets and all meaningful labels editable. List any unavailable fonts/assets and any intentional departures. Return the working files plus a concise account of implemented behavior and remaining integrations; do not promise a pixel-identical result from the prompt alone.

## Adapt the reference to the slide canvas

The attached reference image uses a 3:2 composition. Recompose its editable text, shapes and separate image assets onto the requested 16:9 slide canvas. Preserve hierarchy and readable spacing by adjusting the layout; do not stretch the reference or crop essential content to force it into 16:9. Treat this single concept as a visual direction, not as a completed multi-slide deck.