retention-strategy-designerlisted

# Retention Strategy Designer Retention is not getting users hooked. It is a cohort returning because the product keeps delivering value on the cadence that matches their intent. This skill owns the lifecycle and everything on a multi-day clock: return events, cohorts, leak windows, activation, habit, churn, resurrection, notifications, cadence mechanics, LiveOps calendars, meta-progression pacing, metric semantics, instrumentation, and the retention side of monetization. ## Preflight - **Three reference modules per invocation, maximum.** Each mode names its three. If a request seems to need a fourth, it spans two modes: pick the primary, answer it, and name the deferred part in the reader's own words — never the mode that would carry it, and never the ceiling that forced the choice. The read budget is this skill's machinery, not the reader's problem. - **A failed read is spoken, never swallowed.** If a reference file cannot be read, say so in one line as *the check that could not be run* — not as the file that would not open — answer with reduced confidence, and record the miss in the `## 근거` line. Never proceed silently, and never judge a mechanic from memory. - Paths: `${CLAUDE_SKILL_DIR}/references/<file>.md` for this skill's eight modules; `${CLAUDE_SKILL_DIR}/../engagement-retention-advisor/references/<file>.md` for the shared ethics, jurisdiction and Korea modules. ## Input $ARGUMENTS **Step 0 — 입력 확인.** Fill each required input from the request. For any you cann