Use the Prompt
Add Your Brief
Add your context below. It will be included with the prompt when you copy or download.
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: Roadmap Review Deck.
Required content and structure
Present priorities, dependencies, confidence levels and decisions required.
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: ivory, charcoal and a single lime accent; oversized headlines, deliberate whitespace and clear information hierarchy. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.
Content preparation
Gather priorities, dependencies, delivery states, confidence definitions and decisions that need review. Keep committed work separate from candidate ideas.
Layout and behavior
Organize the roadmap around outcomes and dependencies, using dates only where justified. Show what would change the plan and which decisions unblock the next stage.
Task-specific acceptance check
- Distinguish committed work from exploratory ideas.
- Look for speculative work placed on a precise timeline.
- Test how the deck communicates a slipped dependency without implying that every downstream date remains fixed.
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 Roadmap Review 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: Present priorities, dependencies, confidence levels and decisions required. Use the following task-specific layout guidance when translating the image into editable elements: Organize the roadmap around outcomes and dependencies, using dates only where justified. Show what would change the plan and which decisions unblock the next stage.
Visual direction from the example brief
ivory, charcoal and a single lime accent; oversized headlines, deliberate whitespace and clear information hierarchy.
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. Organize the roadmap around outcomes and dependencies, using dates only where justified. Show what would change the plan and which decisions unblock the next stage. Keep navigation outside exported slide content. Distinguish committed work from exploratory ideas.
Visual comparison and delivery
- 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.
- Then test the narrow layout without squeezing desktop text into tiny labels.
- 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.
Download Prompt + Image
Includes the complete prompt and full-size reference image. Attach both in OpenDesign to guide the layout.
How to Write a Roadmap Review Deck Design Prompt
Use this roadmap review deck design prompt to present priorities, dependencies, confidence levels and decisions required.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Show Commitment Levels Explicitly
A roadmap review deck is a discussion of priorities and uncertainty.
A timeline should not turn exploratory work into a promise simply by placing it on a date. Organize the roadmap around outcomes and dependencies, using dates only where justified. Show what would change the plan and which decisions unblock the next stage.
From the Prompt
Organize the roadmap around outcomes and dependencies, using dates only where justified.
Make It Your Own
Group [INITIATIVES] by priority and commitment level, with dependencies and confidence. Separate committed milestones from exploratory ideas and call out decisions required.
Prepare the Roadmap Review Deck Content
The illustrated road communicates sequence rather than elapsed time; use it for horizons and keep dates in explicit roadmap records.
Gather priorities, dependencies, delivery states, confidence definitions and decisions that need review. Keep committed work separate from candidate ideas.
From the Prompt
Present priorities, dependencies, confidence levels and decisions required.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this roadmap review deck. Gather priorities, dependencies, delivery states, confidence definitions and decisions that need review. Keep committed work separate from candidate ideas. Identify missing inputs before replacing them with demonstration content.
Check a Low-Confidence Initiative
The bottom row outlines the review criteria; separate committed work from exploratory ideas in both labels and discussion.
Its visual treatment should distinguish it from a committed release. The deck should explain what evidence or dependency would make its timing firmer. Look for speculative work placed on a precise timeline. Test how the deck communicates a slipped dependency without implying that every downstream date remains fixed.
From the Prompt
Distinguish committed work from exploratory ideas.
Make It Your Own
Review the roadmap review deck against this requirement: Distinguish committed work from exploratory ideas. Look for speculative work placed on a precise timeline. Test how the deck communicates a slipped dependency without implying that every downstream date remains fixed. Preserve approved content and revise only the parts that fail this check.
Review Your Roadmap Review Deck Result
A generated image cannot validate a complete deck or its evidence. Test every slide, keyboard navigation, print layout and any exported file separately.
- Look for speculative work placed on a precise timeline. Test how the deck communicates a slipped dependency without implying that every downstream date remains fixed.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current roadmap review deck. Look for speculative work placed on a precise timeline. Test how the deck communicates a slipped dependency without implying that every downstream date remains fixed. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
