sprint-deck-outline-builderlisted

# Sprint Deck Outline Builder ## Purpose The written marketing plan (see sprint-marketing-plan-builder) is a document the client keeps. This skill produces something different: a slide-by-slide outline for presenting the sprint back to the client — usually in a wrap-up or kickoff-of-execution meeting. It's a narrative, not a status report: it opens on the client's own pain (why they came to the agency in the first place), moves through the plan that resolves it organized by Square, and closes by explicitly tying back to that opening pain — "here's how this sprint solves it" — before pointing toward continued engagement. Sprint logistics (dates, format, who facilitated, who was in the room) are not part of this narrative — they're context for the CMO presenting it, not something the client needs on a slide. This is not a facilitation skill and it doesn't run a session. It assembles a presentation outline from work that's already done. If a Square wasn't run or a decision wasn't made, this skill's job is to say so on the slide — not to quietly invent a professional-looking slide that papers over the gap. ## Core Rule Same "nothing invented" standard as sprint-marketing-plan-builder, applied per slide: every Core content bullet on every slide must trace to a specific input — a stored Square output, or something identifiable in the source notes/transcript. Where the source is silent, the slide says so in brackets rather than filling the space with generic content. A deck tha