Skip to content

borghei/Claude-Skills / project-management/execution/beta-program

beta-program

Verified

Plan and run a closed beta: cohorts, exit gates agreed before recruiting, weekly cadence and a Greenlight/Extend/Pivot/Kill memo. Use when running a closed beta or design-partner program before general availability.

assets/weekly-cadence-template.md

View on GitHub
# Beta Weekly Cadence Templates

Four templates covering the standard weekly rhythm: Monday digest, Tuesday office hours, Wednesday internal review, Friday snapshot. Copy, fill, send.

---

## Monday Digest (to participants)

> Subject: [Feature] beta -- Week N digest
>
> Hi team,
>
> Welcome to week N of the [Feature] beta. Quick rundown:
>
> **What shipped this week**
> - [Plain-language summary of change 1 -- link to ticket]
> - [Plain-language summary of change 2]
> - [Plain-language summary of change 3]
>
> **Known issues**
> - [Issue 1] -- workaround: [X]. Fix expected [day].
> - [Issue 2] -- workaround: [X]. Fix expected [day].
>
> **What we want you to try this week**
> [One specific task tied to a gate. Example: "Build a dashboard with at least 5 widgets and share it with one teammate. We want to see if the sharing flow holds up."]
>
> **Office hours**
> Tuesday [time] at [link]. Async questions go in #beta-feature-name.
>
> **A learning from last week**
> [One sentence highlighting something we learned from participant feedback, plus the name of the contributor if they consented.]
>
> Thanks for being here.
>
> [PM Name]

---

## Tuesday Office Hours (Agenda)

> **[Feature] Beta Office Hours -- Week N**
>
> Date: [YYYY-MM-DD], [time]
> Host: [PM Name] + [Eng Lead]
> Link: [Zoom / Meet]
>
> **Seed agenda (PM speaks if quiet)**
>
> 1. Quick recap: what shipped this week (2 min)
> 2. Top open question from the Monday digest (5 min)
> 3. Open floor -- anything broken, surprising, or missing? (15 min)
> 4. Preview: what is shipping next week (3 min)
> 5. Wrap and next steps (5 min)
>
> **Notes will be posted in #beta-feature-name within 24 hours.**

---

## Wednesday Internal Review (Agenda)

> **[Feature] Beta Internal Health Review -- Week N**
>
> Date: [YYYY-MM-DD], [time]
> Attendees: PM, Eng Lead, Design Lead, CS Rep, PMM
>
> **1. Gate Metrics (5 min)**
>
> | Gate | Target | Current | Trend |
> |------|--------|---------|:-----:|
> | Activation (% to first action in 7 days) | >= 70% | [X]% | [up/down/flat] |
> | Engagement (median sessions/week) | >= 3 | [X] | [up/down/flat] |
> | Retention (% active in week 4) | >= 60% | [X]% | [up/down/flat] |
> | Outcome (% achieving headline) | >= 50% | [X]% | [up/down/flat] |
> | NPS | >= 30 | [X] | [up/down/flat] |
> | P0 bugs open | 0 | [X] | [up/down/flat] |
> | Crash-free sessions | >= 99.5% | [X]% | [up/down/flat] |
> | Quotable testimonials confirmed | >= 3 | [X] | [up/down/flat] |
>
> **2. Top 3 Bugs by Occurrence (5 min)**
> 1. [Bug] -- N occurrences -- owner: [name] -- target fix: [date]
> 2. [Bug] -- ...
> 3. [Bug] -- ...
>
> **3. Top 3 Feature Requests by Frequency (5 min)**
> 1. [Request] -- N participants -- in scope for beta? [Yes/No/Defer]
> 2. [Request] -- ...
> 3. [Request] -- ...
>
> **4. Risk Register Update (5 min)**
> - [Risk] -- status: [new / mitigating / accepted / closed]
> - [Risk] -- ...
>
> **5. Decision: Are we on track for exit-gate review on [date]? (5 min)**
> - [Yes / Yes with caveats / No, recommend extension]
> - Action items:
>   - [ ] [Owner -- task -- due]
>   - [ ] [Owner -- task -- due]

---

## Friday Snapshot (to participants)

> Subject: [Feature] beta -- Week N snapshot
>
> Quick numbers from week N:
>
> ```
> Activation: [X]% (target: 70%)
> Median sessions/week: [X] (target: 3)
> P0 bugs open: [X] (target: 0)
> ```
>
> **Biggest learning this week**
> [One sentence.]
>
> **Thank you to**
> [Names of 1-3 participants who contributed notable feedback this week, with permission.]
>
> Have a good weekend.
>
> [PM Name]

---

## Thursday 1:1 Template

> **[Feature] Beta 1:1 -- [Participant Name]**
>
> Date: [YYYY-MM-DD]
> Duration: 30 min
>
> **Standing questions (always ask)**
> 1. What is working for you?
> 2. What is broken or frustrating?
> 3. What is missing that you wish were there?
> 4. If we shipped this exactly as it is today, would you renew at the GA price of [$X]?
> 5. Would you recommend this to a colleague? Why or why not?
> 6. Anything you would want me to know that I have not asked?
>
> **Week-specific question (rotate by gate)**
> [E.g., week 3: "We have a draft testimonial: '<quote>'. Could we attribute that to you at launch?"]
>
> **Outcome of this call**
> - Top 3 themes:
>   1. [Theme]
>   2. [Theme]
>   3. [Theme]
> - Quotable feedback? [Yes/No -- if yes, paste quote]
> - Reference candidate? [Yes/No/Maybe]
> - Action items for the team:
>   - [ ] [Owner -- task -- due]
>   - [ ] [Owner -- task -- due]
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall