Primer Brief
Short brief-building prompt for a concise intermediate deck outline.
Show full prompt
Consolidate everything we've agreed in this conversation into a clean, final deck brief that can later be converted into a strict `deck_spec`. Only include the final agreed direction. Ignore earlier ideas, alternatives, dead ends, and discarded content. OBJECTIVE: Create a clear intermediate brief that: - resolves ambiguity - removes duplication - sharpens the storyline - chooses the right slide types - tightens titles and executive-summary wording - keeps the overall pack short and efficient - prepares the material for clean conversion into structured JSON IMPORTANT: - Do not output JSON - Do not output markdown code fences - Do not output alternative options unless explicitly asked - Be decisive and synthesise to one coherent answer - Prefer clean consulting language over brainstorming language - Prefer contractions where natural and professional, such as `aren't`, `can't`, `doesn't`, `it's`, `that's`, and `won't` YOUR JOB: 1. Identify the final deck objective. 2. Define the clearest top-down storyline. 3. Propose the best section structure. 4. Define the cover-slide content. 5. Draft the executive summary so it works as the first content slide after the cover. 6. Recommend the best slide type for each slide. 7. Tighten titles so they are presentation-ready and likely to fit the template. 8. Make sure the brief is clean enough for direct conversion into a `deck_spec`. 9. Keep the total number of slides tight enough for the standard template to feel full rather than sparse. 10. Use the notes field on each slide to capture concise explainer guidance, future iteration ideas, and open questions where helpful. OUTPUT FORMAT: Return the brief using exactly these section headers and structure: DECK META - deck_title: - output_title: - deck_purpose: - audience: - tone: - document_status: PACK TITLE - line_1: - line_2: COVER SLIDE - title: - subtitle: - prepared_for: EXEC SUMMARY - title: - subtitle: - point_1_main: - point_1_detail_1: - point_1_detail_2: - point_2_main: - point_2_detail_1: - point_2_detail_2: - point_3_main: - point_3_detail_1: - point_3_detail_2: - point_4_main: - point_4_detail_1: - point_4_detail_2: SECTION STRUCTURE - section_1: - section_2: - section_3: - optional_section_4: SLIDES For each slide, use exactly this pattern: SLIDE N - slide_type: - section: - title: - subtitle_or_message: - purpose: - key_content: - notes: NOTES RULES - Every slide must include a populated `notes` field. - Use notes to add presenter guidance, important caveats, assumptions, useful future-build considerations, and any open questions that should be revisited later. - Notes should complement the slide rather than repeat it verbatim. - Prefer compact note sections using plain-text headers followed by short lines. - Format notes with simple headings and line breaks, for example: `EXPLAINER` `Short speaker guidance or interpretive framing.` `CONSIDERATIONS` `- Useful enhancement or future build idea` `- Practical thing to test or validate` `OPEN QUESTIONS` `- Key unresolved issue if one exists` - Keep notes readable in PowerPoint notes view: short paragraphs, short bullets, and visible spacing between sections. - Do not force all sections onto every slide; include only the sections that materially help. SLIDE TYPE RULES - Always include exactly one `exec_summary` slide as the first content slide after the cover. - Use `title_section_divider` only when the pack genuinely benefits from section breaks. - Usually use 0-2 section divider slides maximum. - Do not use section dividers in short packs unless they materially improve navigation. - Use `title_full` for narrative explanation and synthesis. - Use `title_2col`, `title_3col`, or `title_4col` only when the content is clearly parallel. - Use `title_2x2` only when a matrix genuinely clarifies the argument. - Use `title_subtitle_table` when the content is best communicated through a compact table. PACK LENGTH RULES - This brief version should stay concise at pack level. - Prefer roughly 4-7 content slides after the cover slide. - Do not stretch a short argument across too many slides just to create space. - If the storyline is short, consolidate related points onto fewer slides rather than spreading them thinly. - Optimise for fuller slides and faster executive consumption, not maximum page count. TITLE RULES - Titles must be argument-led, not topic-led. - Titles should usually fit comfortably within two lines. - Prefer roughly 8-14 words for titles. - Keep titles tighter than the maximum available space. - Use a short full sentence when helpful, but avoid long stacked clauses. EXEC SUMMARY RULES - The 4 main points should tell the story on their own if only they are read. - Each main point can be a short full sentence. - Each corresponding detail should be exactly 2 full bullet points. - Keep the detail bullets concise enough to fit comfortably on the slide. - The exec summary must reflect the key top-down messages supported by the rest of the pack. SECTION DIVIDER RULES - Only include a section divider when a new section genuinely changes the focus of the deck. - Never place section divider slides back to back. - Do not end the deck on a section divider. CONTENT RULES - Keep the pack coherent from top to bottom. - Avoid repetition across slides. - Make the logic cumulative, not circular. - Ensure every slide earns its place in the pack. - Do not artificially limit the number of points within a column if the slide type can support them cleanly.