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.
Pack designTier standardJob Explain it to decision makers, Create on brand collateralv0.1.0
In Claude Code, with the design plugin installed, invoke it as:
/design:slide-outliner
Try it
A realistic prompt from the skill's acceptance evals:
Outline an architecture review deck for our proposed move to event-driven order processing — the audience is staff engineers plus one VP.
What a good result looks like
Slide titles assert, don't label. ✅ "We can ship the migration in two quarters" — ❌ "Migration timeline".
No slide has both "high-level overview" *and* "deep technical detail". Pick one. If you need both, that's two slides.
Speaker notes carry the narrative; slides carry the evidence. Don't put your script on the slide.
One idea per slide. If the slide has two takeaways, split it.
Appendix slides are labeled as such so the presenter doesn't accidentally walk into them.
How it's checked
Measured against plain Claude Code (2026-10-23): it met 64% of its checks, against 75% without it, and a blind judge preferred the agent without it. How skills are checked
17 assertions across 3 acceptance evals, and 8 trigger queries. Every skill's checks
What the output must do
Every slide title asserts a claim rather than labelling a topic ('We can ship this in two quarters', not 'Timeline')
No single slide mixes high-level overview with deep technical detail — where both are needed it becomes two slides
Speaker notes carry the narrative while the slide carries the evidence; the script is not dumped onto the slide
The output is a structured outline the user can paste into their own tool — no .pptx file is produced
Slide count and depth are matched to the stated audience
The outline has no more than 10 slides, each with a title, key points and speaker notes
It does not say the regulator has signed off; it says the application was submitted on 30 September 2026 with a decision expected in Q1 2027, and tells the user why it did not use the director's line
It does not say chlorine is being removed altogether; it makes clear chlorine dosing stays at a lower dose to hold a residual and that it is the gas deliveries that end, and tells the user why
It flags that the capex in the summary and the ask (£4.2m) does not match the cost table (£3.8m) instead of presenting one figure as settled
It states the ask clearly: approve the capex and release £0.6m now for detailed design
It includes the risks from the notes, including the 40-week reactor lead time and the power supply agreement that has not yet been requested
It does not invent figures, dates, names, approvals or benefits that are not in the notes
Gives an outline sized for a 5-minute slot (about 3 to 6 slides), each with a title and what to say
It uses 180 miles a week as given, and any figure it works out from it is correct (for example about 9,360 miles a year) and labelled as an estimate
It does not invent money savings, fuel costs, numbers of cafes or customer feedback; where those would help, it says they would need to be found
It raises the question the managers are likely to ask about how the cafes that now get Tuesday deliveries are affected, rather than ignoring it
It is short, in plain words, and delivers without asking questions first
When it should and shouldn't activate
Should activate:
Outline the slides for my architecture review
Give me slide titles, key points, and speaker notes for this pitch
Structure this into a deck outline I can build from
What slides do I need for this technical presentation?
Should leave to another skill:
Generate the actual .pptx file for me
Write a one-page executive summary of this doc
What are the structural rules for presenting to a board?