Apply working backwards methodology to clarify product vision before building.
Works with
Guides users through the core framework: identify the customer problem, write a mock press release, develop an FAQ, and evaluate three criteria (big idea, strategic fit, viable plan)
Draws on insights from 12 product leaders including Ian McAllister, Bill Carr, and Melanie Perkins on starting with customer problems, defining ideal future states, and escaping incremental thinking
Flags common mistakes like
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionworking-backwardsExecute the skills CLI command in your project's root directory to begin installation:
Fetches working-backwards 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 working-backwards. Access via /working-backwards 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
0
total installs
0
this week
616
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
616
stars
Help the user apply the working backwards methodology using frameworks and insights from 12 product leaders.
When the user asks for help with working backwards:
Ian McAllister: "Working backwards is all about the problem and starting there. Teams that do it wrong don't work backwards - they have something they want to build." Avoid retrofitting a problem to a pre-existing solution. Start with the problem paragraph before defining the solution.
Bill Carr: "Jeff would say, we took it as an article of faith. If we served customers well, things like revenue and share price would follow." Work backward from the ideal customer solution and trust that business metrics will follow.
Christopher Lochhead: "Standing in that future, five years out, looking back to the present, what did we do to make this different future happen? That's how you unshackle yourself from the past." Envision a radical future and work backward without being constrained by current limitations.
Bill Carr: "We're going to start by writing a press release describing the feature in a way that speaks to the customer. The idea better jump off the page as something a customer will really need." Write a problem paragraph, a solution paragraph, a customer quote, and a leadership quote before building anything.
Ian McAllister: "One, is it a big idea? Two, is it something we should be doing? Three, is there a legitimate plan to succeed?" A successful product proposal must pass all three tests. The FAQ proves whether a legitimate plan exists.
Melanie Perkins: "Column B is work from this dream reality and work backwards from how to achieve that." Imagine the 'castle on the hill' - the mythical perfect experience - first, then build rungs on a ladder from today to that vision.
Anuj Rathi: "You're working backwards from an entire machinery at a particular day that is working. What will be the machinery we would have created so that this product is successful?" Working backwards includes GTM strategy, organizational alignment, and stakeholder buy-in, not just the product itself.
Nilan Peiris: "What is the theoretical minimum cost for moving money? What is the theoretical maximum speed? Not just make it instant, make it cheap, but what actually is the lowest it could possibly be?" Define the best possible outcome and work backward from that, not from incremental improvements.
For all 15 insights from 12 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
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Useful defaults in working-backwards — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added working-backwards from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend working-backwards for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for working-backwards matched our evaluation — installs cleanly and behaves as described in the markdown.
working-backwards fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
working-backwards has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend working-backwards for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: working-backwards is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in working-backwards — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: working-backwards is focused, and the summary matches what you get after install.
showing 1-10 of 50