career-transitions▌
refoundai/lenny-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Navigate career transitions using frameworks from 76 product leaders who successfully pivoted roles and industries.
- ›Covers four transition types: new role, new function, new stage, or entirely new path; includes readiness assessment and low-risk experimentation methods
- ›Core principles emphasize progress over pay, relationship-building over linear promotion, and treating your career like a product with testable hypotheses
- ›Provides diagnostic questions to uncover motivations (\"pushes\
Career Transitions
Help the user navigate career changes using frameworks from 76 product leaders who have successfully pivoted roles, industries, and career stages.
How to Help
When the user asks for help with a career transition:
- Identify the type of move - Determine if they're seeking a new role, new function, new stage, or entirely new path
- Understand motivations - Uncover the "pushes" (frustrations) and "pulls" (attractions) driving the change
- Assess readiness signals - Help them evaluate if now is the right time or if preparation is needed
- Design experiments - Suggest low-risk ways to test hypotheses before committing fully
Core Principles
Progress matters more than pay
Bob Moesta: "Over 50% of the people who got new jobs didn't get more money. It's a lie. It's about progress. It's about what do they want to learn? What skills do they want to get?" Identify your "metric of progress" - what growth looks like for you specifically.
Use the Genie Framework
Graham Weaver: "What if you had one wish... whatever you throw yourself into, it's going to turn out great." Remove fear of failure from the equation to identify what you actually want. Work backwards from a successful 10-year outcome.
Build serendipity through relationships
Gokul Rajaram: "Great careers are built by knowing a lot of people doing great work so they know and want you on their teams, and just waiting for serendipity and then seizing it." Prioritize building relationships with smart people over linear promotion paths.
Follow intuition over spreadsheets
Ami Vora: "The thing that has consistently served me is to do the thing that feels right, go to the place that feels like home, work with the people who feel like my friends." Choose roles where you feel "lucky" to be there.
Three months is attainable
Paul Millerd: "A three month sabbatical is much more attainable than people think... if you're assuming you're going to work continuously in adulthood, that's about 500 months." Frame sabbaticals as a tiny fraction of your total career to make them feel possible.
Treat your career like a product
Gibson Biddle: "It's just a lot like building a product. You have theories and hypotheses, you find ways to experiment with them." Run small experiments to test career hypotheses before making big commitments.
Internal moves are easier
Anneka Gupta: "Doing it within the same company is a lot easier than trying to switch companies and switch jobs at the same time because you've already built credibility." Leverage existing relationships and domain knowledge for role transitions.
Balance learning and impact
Deb Liu: "You can have the most impact in the job you know the best, but then you stop learning... How do you keep going back and forth so that you're not going straight up?" Alternate between mastery roles and "newbie" roles to avoid stagnation.
Join winning teams
Matt MacInnis: "As an early career product manager... you should join a winning team. I want to hear what they learned from being part of a winning team." High-growth companies provide more learning than struggling ones.
Questions to Help Users
- "If success were guaranteed, what would you pursue?"
- "What are you running away from versus running toward?"
- "When did you last feel truly energized by your work?"
- "What would you do if you didn't have to make money?"
- "Who are the three people whose careers you most admire?"
- "What's the smallest experiment you could run to test this path?"
Common Mistakes to Flag
- Optimizing for compensation early - Early career earnings are negligible compared to back-loaded executive compensation
- Staying due to inertia - Monitor if your environment still provides learning or if you're the "boiling frog"
- Title chasing - A senior role at a losing company often beats a junior role at a market leader
- Skipping the sabbatical buffer - Moving between intense roles without recalibration leads to carrying old culture baggage
- Ignoring the "habitat" fit - Failing in one environment doesn't mean you lack skills; it may mean wrong environment
Deep Dive
For all 111 insights from 76 guests, see references/guest-insights.md
Related Skills
- Building a Promotion Case
- Negotiating Offers
- Finding Mentors & Sponsors
- Managing Imposter Syndrome
How to use career-transitions on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add career-transitions
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches career-transitions from GitHub repository refoundai/lenny-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate career-transitions. Access the skill through slash commands (e.g., /career-transitions) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★57 reviews- ★★★★★William Smith· Dec 28, 2024
career-transitions has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Li Martin· Dec 16, 2024
I recommend career-transitions for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Mei Gonzalez· Dec 16, 2024
Solid pick for teams standardizing on skills: career-transitions is focused, and the summary matches what you get after install.
- ★★★★★Ganesh Mohane· Dec 12, 2024
I recommend career-transitions for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Mei Mensah· Dec 4, 2024
career-transitions fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Sophia Srinivasan· Nov 23, 2024
Registry listing for career-transitions matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Li Harris· Nov 19, 2024
career-transitions reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Aarav Brown· Nov 19, 2024
Registry listing for career-transitions matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Li Sharma· Nov 7, 2024
Useful defaults in career-transitions — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Rahul Santra· Nov 3, 2024
Useful defaults in career-transitions — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 57