Apply systems thinking frameworks to understand complex multi-stakeholder problems and second-order effects.
Works with
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
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionsystems-thinkingExecute the skills CLI command in your project's root directory to begin installation:
Fetches systems-thinking from refoundai/lenny-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate systems-thinking. Access via /systems-thinking in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
616
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
616
stars
Help the user apply systems thinking to complex problems using frameworks and insights from 6 product leaders.
When the user asks for help with systems thinking:
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.
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.
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.
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.
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.
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.
For all 6 insights from 6 guests, see references/guest-insights.md
Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
We added systems-thinking from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
systems-thinking reduced setup friction for our internal harness; good balance of opinion and flexibility.
systems-thinking has been reliable in day-to-day use. Documentation quality is above average for community skills.
systems-thinking is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: systems-thinking is focused, and the summary matches what you get after install.
systems-thinking fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend systems-thinking for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: systems-thinking is the kind of skill you can hand to a new teammate without a long onboarding doc.
systems-thinking fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
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