Agent skill · marketing growth · borghei
beta-program
Closed beta program playbook covering recruitment, success criteria, communication cadence, and beta-to-GA exit gates.
Why this skill is useful
Provides structured templates and decision rules for managing closed beta programs that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Closed Beta Program Playbook Overview A structured playbook for running a closed beta that produces clear learning, retained design partners, and an unambiguous decision on whether to proceed to general availability. Most betas fail not because the product is wrong, but because the program is run informally: recruitment is opportunistic, success criteria are implicit, communication is sporadic, and exit gates are never defined. This skill replaces all of that with concrete templates and decision rules. A good closed beta runs 4-8 weeks, recruits 10-30 participants from three concentric cohorts ("friends, family, fanatics"), publishes a weekly cadence the team commits to, and exits on pre-agreed criteria rather than the calendar. The outputs are a beta program plan, a recruitment script, a weekly cadence template, and an exit memo that either greenlights GA, extends the beta, or kills the feature. Core Capabilities Cohort design — sequence recruitment through Friends → Family → Fanatics rings of decreasing trust and increasing signal. Kano scoping — decide the beta feature set (Must-be / Performance / Delight) so the beta produces quotable testimonials, not neutral feedback. Exit gates — quantitative + qualitative success criteria set before recruitment, resolving to Greenlight / Extend / Pivot / Kill. Weekly cadence — a committed Monday→Friday communication rhythm that keeps a beta from dying of silence. When to Use Pre-GA validation -- A feature has cleared internal alpha but needs external validation under real workloads before a public launch. High-risk feature -- Significant blast radius, regulatory exposure, or pricing changes that warrant a controlled rollout to a small group first. Design partner program -- Recruiting a small set of customers whose feedback shapes v1 scope and pricing. Enterprise rollout -- New module that needs reference customers and case studies before broad sales enablement. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/beta-program