systems-thinking▌
refoundai/lenny-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Apply systems thinking frameworks to understand complex multi-stakeholder problems and second-order effects.
- ›Maps systems by identifying all players, their incentives, and interactions; traces stocks (what accumulates) and flows (what moves between states)
- ›Helps identify leverage points where small interventions create large systemic changes and uncover feedback loops that amplify or dampen outcomes
- ›Flags common mistakes including optimizing locally, ignoring incentives, treating sym
Systems Thinking
Help the user apply systems thinking to complex problems using frameworks and insights from 6 product leaders.
How to Help
When the user asks for help with systems thinking:
- Map the system - Help them identify all players, their incentives, and how they interact with each other
- Identify stocks and flows - Understand what accumulates (stocks) and what moves between states (flows)
- Trace second-order effects - Work through what happens after the first-order impact of any change
- Find leverage points - Identify where small interventions can create large systemic changes
Core Principles
See the system
Seth Godin: "What does it mean to be a strategic thinker? It means to see the system." Understanding the invisible rules, culture, and interoperability that govern how products and organizations succeed or fail is the foundation of strategic thinking.
Think about all players and incentives
Sriram: "Systems thinking. Think of all the players in the system, think of all of their incentives and how they interact with each other." This approach is superior to Jobs-to-be-Done for handling complex product trade-offs and multi-agent incentives.
Use stocks and flows
Will Larson: "Systems thinking is basically you try to think about stocks and flows. Stocks are things that accumulate and flows are the movement from a stock to another thing." Model business processes like hiring pipelines or user funnels using this framework.
Consider second, third, and fourth-order effects
Hari Srinivasan: "The skillsets that you think through and manage in a complicated ecosystem are quite different." Managing complex ecosystems requires understanding effects that cascade beyond the immediate impact.
Think beyond today's decisions
Nickey Skarstad: "Second order thinking is you being able to think beyond the decisions that you're making today." Consider how current decisions impact future constraints and ecosystem dynamics.
Automate recurring pains
Melissa Perri + Denise Tilles: "Tell me about some process you really hated and ended up trying to automate or build a system around to make it better." Identify recurring manual pains and build automated systems or frameworks to solve them.
Questions to Help Users
- "Who are all the players in this system, and what does each one want?"
- "If you make this change, what happens next? And then what happens after that?"
- "What accumulates over time in this system (the stocks), and what flows between states?"
- "Where are the feedback loops - both reinforcing and balancing?"
- "What constraint, if removed, would unlock the most value in this system?"
- "What recurring manual pain could be systematized?"
Common Mistakes to Flag
- Only seeing first-order effects - Changes ripple through systems in ways that aren't immediately obvious
- Ignoring incentives - Every player in a system responds to their own incentives, not yours
- Optimizing locally - Improving one part of a system can make the whole system worse
- Missing feedback loops - Many systems have self-reinforcing or self-balancing dynamics that amplify or dampen changes
- Treating symptoms instead of causes - Systems problems often require addressing root causes, not visible symptoms
Deep Dive
For all 6 insights from 6 guests, see references/guest-insights.md
Related Skills
- Setting OKRs & Goals
- Defining Product Vision
- Platform Strategy
- Organizational Design
How to use systems-thinking 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 systems-thinking
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches systems-thinking 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 systems-thinking. Access the skill through slash commands (e.g., /systems-thinking) 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.6★★★★★71 reviews- ★★★★★Chaitanya Patil· Dec 28, 2024
We added systems-thinking from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Hassan Johnson· Dec 24, 2024
systems-thinking reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Yusuf Tandon· Dec 20, 2024
systems-thinking has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Layla Perez· Dec 20, 2024
systems-thinking is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Hassan Smith· Dec 16, 2024
Solid pick for teams standardizing on skills: systems-thinking is focused, and the summary matches what you get after install.
- ★★★★★Fatima Shah· Dec 16, 2024
systems-thinking fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Li Anderson· Dec 4, 2024
I recommend systems-thinking for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Fatima Singh· Nov 23, 2024
Keeps context tight: systems-thinking is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Piyush G· Nov 19, 2024
systems-thinking fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Li Smith· Nov 19, 2024
Useful defaults in systems-thinking — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 71