sprint-deliverables-builderlisted

# Sprint Deliverables Builder ## Purpose A Fractional CMO ran a Marketing Strategy Sprint live with their client — in person, over a call, however — outside of Claude entirely. What lands in this conversation afterward is the record of that session: a transcript, Gemini/Otter notes, or similar. This skill's job is to turn that single input into the two deliverables the CMO sends the client: the written Marketing Plan document and the recap slide deck — built together, in the right order, so they never quietly disagree with each other. This skill does no facilitation and makes no judgment calls of its own about what was decided — that's entirely the job of the two skills it calls. It exists purely to remove the manual step of invoking them separately and making sure the second one reuses the first one's extraction instead of re-deriving its own version of the same facts. ## Why Order Matters sprint-marketing-plan-builder and sprint-deck-outline-builder can each work standalone from a raw transcript — that's how they were each built and tested. But when both are wanted from the same transcript in the same sitting, running them independently risks drift: each one re-reads the transcript on its own, and two independent readings of "was the warranty bundling decision aligned or still open" can come back with subtly different phrasing or, worse, a different status. Both skills already anticipate this and say to reuse a same-session extraction when one exists — this skill's who