sprint-marketing-plan-builderlisted

Turns a completed (or partially completed) Marketing Strategy Sprint into a written marketing plan document the client keeps — a Square-by-square (TREC) record of decisions, consolidated objectives, a time-bound Strategy Activation Plan (dated goal cascade with checklist tactics), open decisions, and next steps, delivered as a polished PDF. Use when someone wants a marketing plan document, strategy document, or activation plan written up from a sprint; trigger on "write up the marketing plan", "turn this sprint into a plan doc", "build the strategy activation plan", "document what we decided", "marketing plan for [client]", or similar, even if "sprint" isn't said explicitly but Square/TREC decisions clearly need documenting. Do NOT trigger for the slide deck version — use sprint-deck-outline-builder for that instead (same source material, different artifact). Do NOT trigger for live facilitation of any Square.
chadjardine/marketing-strategy-sprint · ★ 0 · Web & Frontend · score 70

Install: claude install-skill chadjardine/marketing-strategy-sprint

# Sprint Marketing Plan Builder ## Purpose This is the document the client keeps and refers back to — as opposed to sprint-deck-outline-builder, which produces a slide deck for walking the client through the same material live. The two are commonly requested together from the same source material, and should stay consistent with each other (see Inputs below), but this skill owns the canonical written record: what was decided Square by Square, the objectives that fall out of those decisions, a time-bound activation plan for executing on them, what's still unresolved, and what happens next. This is not a facilitation skill and it doesn't run a session. It assembles a document from work that's already done. If a Square wasn't run or a decision wasn't made, this document's job is to say so — not to quietly invent professional-looking content that papers over the gap. A polished document that misrepresents what was actually decided is worse than an honest one with visible gaps — it tells the client something was decided when it wasn't, in a document they'll reference for months. ## Core Rule Every substantive claim in this document — every goal, date, number, decision, or tactic — must trace to a specific input: a stored Square skill output, or something identifiable in the source sprint notes/transcript. Where the source is silent, say so explicitly ("timing not specified," "not yet addressed this sprint") rather than filling the gap with generic, plausible-sounding content.