Help teams create written technical roadmaps aligned to business outcomes using structured frameworks.
Works with
Applies the Rumelt framework to organize strategy into three parts: Diagnosis (core technical challenge), Guiding Policies (decision-making principles), and Actions (specific initiatives)
Emphasizes documenting strategy in writing so it can be critiqued, improved, and aligned across teams rather than existing only in leadership's head
Flags common pitfalls including tool proliferati
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiontechnical-roadmapsExecute the skills CLI command in your project's root directory to begin installation:
Fetches technical-roadmaps 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 technical-roadmaps. Access via /technical-roadmaps 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 create effective technical roadmaps using frameworks and insights from 1 product leader.
When the user asks for help with technical roadmaps:
Will Larson: "The first rule of strategy is that if you write it down, then you can improve it. If it's not written down, it's hard to say if this PM is just not a good PM or if they're trying to apply a strategy they've misunderstood." A written strategy provides a baseline that can be critiqued and improved.
Will Larson: "A common strategy that's really good but very boring is we only use the tools we have today. Engineers want to introduce new programming languages, new databases, new cloud providers. A really good strategy for almost all companies is we just use the standard kit we already have." Focus engineering energy on business-valued problems rather than technical novelty.
Structure technical strategy using Richard Rumelt's framework: Diagnosis (what's the core challenge?), Guiding Policies (what principles will guide decisions?), and Actions (what specific things will you do?).
Define a list of approved tools, languages, and platforms. This limits technical sprawl and allows teams to focus on solving core product problems rather than reinventing infrastructure.
For all 2 insights from 1 guest, 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
I recommend technical-roadmaps for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
technical-roadmaps has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: technical-roadmaps is focused, and the summary matches what you get after install.
technical-roadmaps has been reliable in day-to-day use. Documentation quality is above average for community skills.
technical-roadmaps is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
technical-roadmaps fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added technical-roadmaps from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in technical-roadmaps — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: technical-roadmaps is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for technical-roadmaps matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 51