Create a detailed presentation plan before generating slides
Generates a detailed presentation plan by gathering requirements and creating a structured blueprint for slide generation.
/plugin marketplace add clearfunction/cf-devtools/plugin install cf-devtools@cf-devtools[topic] e.g., 'React hooks' or 'our authentication system'slidev/Create a detailed presentation plan for: $ARGUMENTS
This plan document serves as the blueprint for slide generation and presenter notes.
Use AskUserQuestion to gather:
Q1: Duration "How long is this presentation?"
Q2: Audience "Who is the target audience?"
Q3: Format "What's the presentation format?"
Q4: Context "What's the venue/occasion?"
Q5: Core Message "What's the ONE thing you want the audience to remember?"
Q6: Call to Action "What should the audience DO after this presentation?"
Q7: Key Topics (multi-select if applicable) "What topics must be covered?"
Q8: Exclusions "Anything to explicitly AVOID or skip?"
Q9: Code Examples "How much code should appear in slides?"
Q10: Live Demo "Will there be live demonstrations?"
Create a file named {topic}-presentation-plan.md with this structure:
# {Title} - Presentation Plan
**Duration:** {X} minutes
**Audience:** {description}
**Format:** {format type}
**Venue:** {context}
---
## Core Message
> "{The ONE thing to remember}"
## Call to Action
{What audience should do after}
---
## Time Allocation
| Section | Time | Focus |
|---------|------|-------|
| 1. Opening Hook | X min | Grab attention |
| 2. Context/Problem | X min | Why this matters |
| 3. Main Content | X min | Core material |
| 4. Demo/Examples | X min | Show, don't tell |
| 5. Wrap-up | X min | Key takeaways |
---
## Section 1: Opening Hook ({X} min)
### Hook Options
**Option A - Problem Statement:**
> "{A compelling problem statement}"
**Option B - Story:**
> "{A relatable story or scenario}"
**Option C - Statistic:**
> "{A surprising fact or number}"
### Context to Establish
- {Point 1}
- {Point 2}
---
## Section 2: {Section Name} ({X} min)
### Key Points
- {Point 1}
- {Point 2}
### Visuals Needed
- [ ] {Diagram: description}
- [ ] {Code example: description}
- [ ] {Screenshot: description}
### Talking Points
- {Note for presenter}
---
## Section 3: {Continue for each section...}
---
## Demo Plan (if applicable)
### Demo Option A: {Name}
- What to show: {description}
- Commands/steps: {list}
- Fallback if fails: {backup plan}
### Demo Backup Plan
- Screenshots prepared: [ ]
- Recording available: [ ]
- Explanation script: [ ]
---
## Diagrams to Create
1. **{Diagram Name}** - {Purpose}
- Type: {Mermaid flowchart/sequence/architecture}
- Key elements: {list}
2. **{Diagram Name}** - {Purpose}
...
---
## Code Examples to Include
1. **{Example Name}** ({language})
- Purpose: {what it demonstrates}
- Lines to highlight: {which parts}
- Progressive reveal: {yes/no}
---
## Potential Q&A
### Anticipated Questions
1. **"{Question}?"**
- Answer: {response}
2. **"{Question}?"**
- Answer: {response}
---
## Presenter Checklist
### Before Presentation
- [ ] Run through entire presentation
- [ ] Test all demos
- [ ] Prepare backup screenshots
- [ ] Increase font sizes
- [ ] Close unnecessary apps
### During Presentation
- [ ] Start with the hook, not introductions
- [ ] Pause after each major section
- [ ] Make eye contact
- [ ] Speak slower than normal
---
## Appendix: Slide Outline
1. Title slide
2. {Slide 2 title}
3. {Slide 3 title}
...
---
_Plan created: {date}_
_Ready for slide generation: [ ]_
Save as {topic-slug}-presentation-plan.md in the current directory.
Inform the user:
Plan created: {filename}
Review the plan and make any edits. When ready, run:
/slidev:from-plan {filename}