Apply working backwards methodology to clarify product vision before building.
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
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
Submit your Claude Code skill and start earning
epx add refoundai/lenny-skills --skill working-backwardsCompatible with
Supported agents
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:
epx add refoundai/lenny-skills --skill working-backwardsFetches 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:
.cursor/skills/working-backwards
Restart Cursor to activate working-backwards. Access via /working-backwardsin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Time estimate: 30-60 minutes to see productivity improvements
Prerequisites
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.
pwa-expert
erichowens/some_claude_skills · Productivity · same category
vite
uni-helper/skills · Productivity · same category
filament-pro
marcelorodrigo/agent-skills · Productivity · same category
lua
mindrally/skills · Productivity · same category
electron-best-practices
jwynia/agent-skills · Productivity · same category
modly-image-to-3d
aradotso/trending-skills · Productivity · same category
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