Use this skill when reproducing runtime-bundle, module-resolution, or user-bundle inclusion regressions.
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 vercel/next.js --skill runtime-debugCompatible with
Supported agents
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionruntime-debugExecute the skills CLI command in your project's root directory to begin installation:
epx add vercel/next.js --skill runtime-debugFetches runtime-debug from vercel/next.js 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/runtime-debug
Restart Cursor to activate runtime-debug. Access via /runtime-debugin 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.
deslop
cursor/plugins · Productivity · same category
premortem
parcadei/continuous-claude-v3 · Productivity · same category
nestjs-best-practices
kadajett/agent-nestjs-skills · Productivity · same category
lua
mindrally/skills · Productivity · same category
business-analyst
404kidwiz/claude-supercode-skills · Productivity · same category
stock-analysis
liusai0820/stock-analysis-skill · Productivity · same category
Registry listing for runtime-debug matched our evaluation — installs cleanly and behaves as described in the markdown.
runtime-debug reduced setup friction for our internal harness; good balance of opinion and flexibility.
runtime-debug fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added runtime-debug from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
runtime-debug fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
runtime-debug reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for runtime-debug matched our evaluation — installs cleanly and behaves as described in the markdown.
runtime-debug fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added runtime-debug from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for runtime-debug matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 70