| name | early-access-designer |
| slug | aaron-early-access-designer |
| displayName | Early Access Designer · 抢先体验设计 |
| summary | waitlist/内测阶梯/毕业标准/反馈闭环 |
| description | Use when the user asks to "design an early access program", "set up a waitlist and beta stages", or "define beta graduation criteria"; produces a waitlist→concept→alpha→beta→GA stage ladder with per-stage purpose and opt-in semantics, quantified graduation criteria per stage (labeled Estimated), a cohort-gating and invite-throttling plan, tester recruitment with launch-day social-proof prep, a feedback-loop spec where every status change notifies its subscribers, and a referral-loop mechanism spec (invite codes, anti-abuse). Not for waitlist acquisition strategy or the capture-flow spec — use list-growth-designer; not for the canonical stage record — use launch-registry. waitlist/内测阶梯/抢先体验/毕业标准/反馈闭环 |
| version | 20.1.0 |
| license | Apache-2.0 |
| compatibility | Claude Code and compatible agent-skill hosts |
| homepage | https://github.com/aaron-he-zhu/aaron-marketing-skills |
| when_to_use | Use when designing how a product moves from waitlist to GA: the stage ladder (waitlist / concept / alpha / beta / GA), per-stage graduation criteria, cohort gating and invite throttling, tester recruitment and launch-day social-proof prep, the tester feedback loop, and referral invite mechanics. The upstream of the RAMP R1 stage-truth veto — stage definitions are submitted to launch-registry as candidates. |
| argument-hint | <product / current stage / launch goal> [audience] [platform] |
| metadata | {"author":"aaron-he-zhu","version":"20.1.0","discipline":"launch","phase":"research","geo-relevance":"low","hermes":{"tags":["marketing","launch","research"],"category":"launch"},"openclaw":{"emoji":"🚀","homepage":"https://github.com/aaron-he-zhu/aaron-marketing-skills"}} |
Early Access Designer
Designs the early-access program for a product launch — the waitlist → concept → alpha → beta → GA stage ladder, per-stage graduation criteria, cohort gating and invite throttling, the tester feedback loop, and the referral mechanics that fill the next cohort. It sits in the Research phase of the RAMP loop and feeds the RAMP R early-access sub-item (early-access program design sound — stage gating + graduation criteria). Because the ladder defines what each stage publicly means, it is the upstream of the RAMP-R1 stage-truth veto: a beta dressed as GA fails at the gate, and the honest ladder designed here is what prevents that.
The ladder follows an early-access state-machine pattern (modeled on the PostHog Early Access flow — a pattern to follow, not a product guarantee): interest registration and stage opt-in are phases of the same action, not separate lists; an explicit opt-in or opt-out always overrides any targeting rule; and a GA rollout must explicitly confirm whether previously opted-out users are included before it ships.
Scope guard: this skill designs the stage ladder, graduation criteria, cohort gating, feedback-loop spec, and referral mechanics only. It does not own the waitlist acquisition strategy or the compliant capture-flow spec (that is list-growth-designer), build the signup page / popup UX (landing-optimizer), record the opt-in (consent-registry is the sole writer of memory/consent/), model the referral economics — K-factor, payout (newsletter-monetization-planner), hold the canonical stage record (launch-registry is the sole writer of memory/launch-registry/), or compute the RAMP profile result (launch-readiness-auditor). It works one lever — the stage ladder — and hands off.
Quick Start
Design an early access program for [product]. Current stage: [waitlist / private beta / none]. Goal: GA by [date].
