launch-retrospectivelisted

Use after a social launch, campaign, creator collaboration, or distribution test has enough evidence to decide what should be repeated, changed, or stopped. Trigger phrases include "run a launch retro", "what did we learn from this campaign?", "postmortem this launch", "should we repeat this?", and "turn these results into next steps". Do not use this to assign blame, invent missing data, or write a live performance dashboard; use social-analytics-report for the in-flight metric read and campaign-brief to plan the next campaign.
Ootto-AI/claude-content-skills · ★ 26 · Testing & QA · score 80

Install: claude install-skill Ootto-AI/claude-content-skills

# Launch Retrospective Turn a completed campaign into durable operational learning: what happened, why it may have happened, and the next smallest decision. ## 1. Reconstruct the intended plan Bring together the original objective, audience, approved message, channel roles, budget or partner scope where supplied, timing, measurement plan, and decisions made during execution. Compare what actually shipped with what was planned. Separate a deliberate change from an accidental deviation. ## 2. Gather the evidence with limits attached Use available performance data, qualitative feedback, partner notes, approvals, and execution records. State dates, metric definitions, missing data, and material confounders. Keep a timeline so the team does not attribute an outcome to a change that happened after it. ## 3. Distinguish facts from explanations List observations first: what was published, what audiences did, and what tracking shows. Then list hypotheses about message, format, distribution, timing, destination, or process. Give each hypothesis a confidence level and the evidence that would strengthen or weaken it. ## 4. Commit to operational changes Return a short set of keep, change, test, and stop decisions with owners and due dates. Update reusable inputs such as the campaign brief template, proof library, UTM vocabulary, or creator brief. Leave a clear record of unresolved questions so they are not rewritten as facts next time. ## Hard rules - Do not use a retrospective