القائمة
Plans beta launches with user recruitment, feedback collection, bug reporting, and iteration cycles. Use when preparing to launch a product or feature in beta.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
A demo skill for tests.
Writes website accessibility policies with WCAG compliance commitments and accommodation procedures. Use when creating an accessibility statement for your website.
Creates a complete client onboarding system for agencies and service providers, including welcome email sequence, intake questionnaire, kickoff meeting checklist, and communication guidelines. Use when a user runs an agency, consultancy, or service business and needs to standardize how new clients are brought on board.
Facilitates annual business planning with vision setting, goal cascading, quarterly milestones, and resource allocation for focused execution.
Compiles annual business reviews with year-over-year metrics, milestone highlights, lessons learned, and strategic goals for the upcoming year. Use when a user needs to reflect on their business year, wants to create a year-in-review document for stakeholders, or is setting annual goals and needs to assess where they stand.
Creates API documentation templates with endpoint descriptions, request/response examples, and authentication guides. Use when documenting REST APIs for developers.
| name | beta-launch-plan |
| description | Plans beta launches with user recruitment, feedback collection, bug reporting, and iteration cycles. Use when preparing to launch a product or feature in beta. |
| allowed-tools | Read Write Glob |
| metadata | {"author":"Salah-XD","version":"1.0"} |
Use this skill when you need to:
DO NOT use this skill for full product launches, alpha/internal testing plans, or QA test plans. This is for external beta launch planning only.
A BETA IS NOT A SOFT LAUNCH — IT IS A STRUCTURED LEARNING PERIOD WITH DEFINED GOALS, SELECTED USERS, AND CLEAR EXIT CRITERIA.
| Input | What to Ask | Default |
|---|---|---|
| Product/feature | "What are you launching in beta?" | No default — must be provided |
| Beta goals | "What do you need to learn from this beta? Validate demand, find bugs, test UX?" | Validate core workflow and identify critical bugs |
| Target beta size | "How many beta users do you want?" | 20-50 users |
| Beta duration | "How long should the beta run?" | 4 weeks |
| Ideal beta user | "Describe your ideal beta tester — role, tech comfort, use case." | Early adopter, tolerant of bugs, willing to give feedback |
| Known risks | "What are you most worried about?" | Core functionality breaking under real usage |
GATE: Confirm the brief before building the plan.
## Beta Timeline
**Week -2 to -1: Pre-Launch**
- Finalize beta criteria and success metrics
- Build feedback collection system
- Recruit and select beta users
- Prepare welcome materials
**Week 1: Controlled Launch**
- Onboard first cohort (50% of total)
- Daily monitoring for critical issues
- First feedback check-in (Day 3)
**Week 2: Expand**
- Onboard remaining beta users
- First iteration based on Week 1 feedback
- Structured feedback survey
**Week 3-4: Iterate and Evaluate**
- Ship fixes and improvements
- Final feedback survey
- Evaluate against success criteria
- Decision: ship, extend, or pivot
Define measurable exit criteria:
| Metric | Target | Measurement |
|---|---|---|
| Critical bugs | 0 unresolved | Bug tracker |
| Task completion rate | 80%+ | User testing |
| NPS score | 30+ | Survey |
| Active usage | 60%+ of beta users engaged weekly | Analytics |
| Feedback sentiment | Mostly positive | Qualitative review |
GATE: Confirm timeline and success criteria before designing recruitment and feedback systems.
Application form fields:
Selection criteria:
Recruitment channels:
Structured feedback:
Unstructured feedback:
Bug Report Template:
**What happened:**
**What you expected:**
**Steps to reproduce:**
1.
2.
3.
**Screenshot (if applicable):**
**Device/browser:**
## Go/No-Go Criteria
**Ship to GA if:**
- [ ] All critical bugs resolved
- [ ] Task completion rate exceeds 80%
- [ ] NPS is 30 or above
- [ ] No data loss or security issues
- [ ] Onboarding flow works without hand-holding
**Extend beta if:**
- [ ] 1-2 critical issues remain but are solvable in 1-2 weeks
- [ ] Usage is strong but feedback reveals UX confusion
- [ ] Need more data to validate a key assumption
**Pivot or kill if:**
- [ ] Core value proposition is not validated
- [ ] Beta users are not using the product despite reminders
- [ ] Critical technical limitation cannot be resolved
## Beta Launch Checklist
- [ ] Success criteria defined with measurable targets
- [ ] Beta user application form is live
- [ ] Selection criteria documented
- [ ] Feedback collection system is set up (survey, widget, bug form)
- [ ] Welcome email drafted and scheduled
- [ ] Weekly update template created
- [ ] Bug report template provided to all beta users
- [ ] Go/no-go decision framework agreed on
- [ ] Beta appreciation plan defined
- [ ] Timeline has clear start, checkpoints, and end date
Product: AI-powered meeting note-taker for solopreneurs Beta size: 30 users, 4 weeks
Welcome email excerpt: "You are one of 30 people testing MeetingMind before anyone else. Over the next 4 weeks, use it in your real meetings. Things will break — that is the point. Report bugs with the red button in the bottom-right corner. Every Friday, you will get a 3-question survey. Your feedback directly shapes what we ship."
Weekly survey: