← ClaudeAtlas

slide-outlinerlisted

Outline an architecture review or technical pitch deck — slide titles, key points per slide, and speaker notes. Does NOT generate PowerPoint/Keynote files; produces a structured outline the user can paste into any deck tool. Use when the user is preparing for an architecture review, design review, sales pitch, partner meeting, or steering-committee presentation.
sananthanarayan/skilldrop · ★ 2 · Code & Development · score 75
Install: claude install-skill sananthanarayan/skilldrop
# slide-outliner You help the user plan a deck before they open PowerPoint, by producing a slide-by-slide outline with structure, key points, and speaker notes. ## How to respond 1. **Pin down audience + format + time.** - **Audience:** engineering peers? execs? customers? regulators? Mix? - **Format:** live presentation (with discussion) vs. read-ahead doc vs. async share? - **Time:** 10 minutes? 30? 60? — this determines slide count more than anything else. Rough guide: **1.5–2 minutes per slide** in a live setting with Q&A. So 30 minutes → 12–15 content slides max, including the cover and the close. 2. **Default structure for an architecture review:** see [`templates/deck-outline.md`](templates/deck-outline.md). Sections in order: 1. **Cover** — title, presenter, audience, date 2. **Why we're here** — the question/decision/approval being sought (one slide) 3. **Context** — what's the current state, what changed, what's the forcing function (1–2 slides) 4. **Proposed approach** — the architecture / decision / change (3–5 slides — this is the bulk) 5. **Alternatives considered** — the strongest 1–2, and why we didn't pick them (1 slide each, max) 6. **Risks & mitigations** — pick the 3–4 the audience cares most about (1 slide) 7. **Cost, timeline, rollout** (1 slide) 8. **What we need from you** — the Ask (1 slide) 9. **Appendix** — backup slides for deep-dive questions (not part of the planned flow) 3. **Per slide, produce:**