Menu
Create executive stakeholder updates following proven communication frameworks. Use when the user needs to create a status update, progress report, executive summary, or communication for leadership, stakeholders, or executives.
Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality.
This skill should be used when the user asks to "generate tests", "write unit tests", "analyze test coverage", "scaffold E2E tests", "set up Playwright", "configure Jest", "implement testing patterns", or "improve test quality". Use for React/Next.js testing with Jest, React Testing Library, and Playwright.
Test-driven development workflow with test generation, coverage analysis, and multi-framework support
Analyze competitors and create competitive landscape documentation. Use when the user asks to analyze competitors, create competitive analysis, compare features with competitors, track competitive landscape, or understand competitive positioning.
Structure and format meeting notes following PM best practices. Use when the user needs to create, format, or organize meeting notes, capture action items from meetings, or document discussions and decisions.
Product Requirements Document creation following proven PM template structure. Use when the user asks to create, write, draft, or help with a PRD, product requirements document, product spec, feature specification, or product documentation for a new feature or product.
| name | stakeholder-update |
| description | Create executive stakeholder updates following proven communication frameworks. Use when the user needs to create a status update, progress report, executive summary, or communication for leadership, stakeholders, or executives. |
This skill creates effective status updates for executives and stakeholders following the BLUF (Bottom Line Up Front) principle.
Start with the most important information:
Brief overview of accomplishments:
Keep to 3-5 bullet points maximum.
Key Metrics
| Metric | Current | Target | Trend | Status |
|---|---|---|---|---|
| [Metric name] | [Value] | [Target] | ↑/→/↓ | 🟢/🟡/🔴 |
Include 3-5 most important metrics only.
High Priority Issues:
Only include issues that matter at executive level.
Next 30 Days:
Next 90 Days:
Tone: Professional, concise, action-oriented Length: Keep under 1 page (or 2 minutes reading time) Frequency: Weekly for active projects, bi-weekly for maintenance
Executive Communication Principles:
Lead with conclusions, not process
Focus on impact, not activities
Make problems visible early
Use data to tell story
Make it scannable
🟢 On Track: Meeting all targets, no significant risks 🟡 At Risk: Potential issues that could impact delivery 🔴 Blocked: Critical issues preventing progress, needs intervention
# Product Update: Customer Onboarding Redesign
**Week of Jan 20, 2026**
## BLUF
**Status**: 🟡 At Risk
**Key Takeaway**: New onboarding flow is performing well in tests (+35% completion), but launch delayed one week due to integration issues with billing system.
**Action Needed**: Decision needed on whether to launch onboarding separately or wait for billing integration fix.
## Progress Summary
- Completed user testing with 24 participants (94% positive feedback)
- Implemented first-time user experience improvements
- Resolved 12 of 15 bugs identified in QA
- Engineering allocated resources to billing integration fix
## Key Metrics
| Metric | Current | Target | Trend | Status |
|--------|---------|--------|-------|--------|
| Onboarding Completion | 45% | 60% | → | 🟡 |
| Time to First Value | 4.2 min | 3.0 min | ↓ | 🟢 |
| Setup Support Tickets | 45/week | <30/week | ↓ | 🟢 |
| User Activation Rate | 52% | 65% | → | 🟡 |
## Risks & Blockers
**HIGH: Billing System Integration Delay**
- **Impact**: Prevents users from completing onboarding flow; delays launch by 1-2 weeks
- **Root Cause**: API deprecation by payment processor, requires code rewrite
- **Mitigation**: Engineering team reallocated resources, fix ETA Feb 3
- **Decision Needed**: Launch onboarding without payment integration or wait for fix? (See below)
**MEDIUM: Mobile Testing Coverage**
- **Impact**: Some edge cases on older Android devices not tested
- **Mitigation**: Partnering with QA to expand test matrix; running beta with internal users on diverse devices
## Upcoming Milestones
**Next 30 Days:**
- Resolve billing integration (Feb 3)
- Launch onboarding redesign (Feb 5 or Feb 12 depending on decision)
- Begin measuring impact on conversion (Feb 12)
**Next 90 Days:**
- Iterate based on production data (March)
- Extend to mobile app (April)
- Launch advanced features (May)
## Decision Needed
**Should we launch onboarding separately from billing integration?**
**Option A: Launch Now (Recommended)**
- Pros: Get 35% completion rate improvement to users immediately, gather production data, maintain momentum
- Cons: Users need to complete payment in old flow, slightly disjointed experience
- Timeline: Launch Feb 5
**Option B: Wait for Billing Fix**
- Pros: Fully integrated experience from day one, no technical debt
- Cons: Delays benefits by 2 weeks, Q1 metric targets at risk, team momentum lost
- Timeline: Launch Feb 12
**Recommendation**: Option A. The onboarding improvements are valuable independently, and the old payment flow works fine. Waiting risks missing Q1 targets and delays validated improvements from reaching users.
**Timeline**: Need decision by Jan 22 for Feb 5 launch.
---
**Questions?** Reply to this email or ping me on Slack.
Daily standups:
Weekly updates:
Monthly reviews:
Quarterly business reviews: