Skill: steering-deck

Skill: steering-deck

Purpose

Build a concise, structured steering committee deck that drives decisions — not just updates.

When to Use

• Monthly or quarterly steering committee meetings
• Go/No-Go decision meetings
• Major scope or timeline change requiring approval

Framework: Steering Committee Deck

Principle

A steering deck is not a status report. It is a decision-support document. Every slide should answer: "What do you need from us?"

Slide Structure (6 Slides Max)

---

Slide 1 — Executive Dashboard

• Programme/Release name
• Overall RAG status
• Date vs forecast
• Budget vs forecast
• Top risk in one line

---

Slide 2 — Progress Since Last Meeting

• What was committed → what was delivered
• Key milestones achieved
• Keep to 4–5 bullet points

---

Slide 3 — Risks & Issues Table format:

Risk/Issue	Status	Impact	Mitigation	Owner
Maximum 3–4 rows. If more exist, say "Full risk register available on request."

---

Slide 4 — Decisions Required This is the most important slide. Format each decision as:

• Decision: [What needs to be decided]
• Options: [Option A vs Option B]
• Recommendation: [Your recommendation]
• Deadline: [Date decision is needed]
• Impact if delayed: [What happens if no decision by then]

---

Slide 5 — Next Period Plan

• What will be completed before next steering meeting
• Key milestones and owners
• Any dependencies on steering committee

---

Slide 6 — Appendix (Optional)

• Detailed risk register
• Full milestone plan
• Team capacity summary

---

Design Principles

• One message per slide
• Max 5 bullet points per slide
• Always include the date
• RAG status visible on every slide (header or footer)
• No walls of text

Output Format

1. Slide-by-slide content (ready to paste into PowerPoint / Google Slides)
2. Speaker notes for each slide (2–3 sentences)
3. Suggested next command: /decision-log or /status-update