Key benefits:
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 neolabhq/context-engineering-kit --skill sadd:do-in-parallelCompatible with
Supported agents
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionsadd:do-in-parallelExecute the skills CLI command in your project's root directory to begin installation:
epx add neolabhq/context-engineering-kit --skill sadd:do-in-parallelFetches sadd:do-in-parallel from neolabhq/context-engineering-kit 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/sadd:do-in-parallel
Restart Cursor to activate sadd:do-in-parallel. Access via /sadd:do-in-parallelin 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
nutritional-specialist
ailabs-393/ai-labs-claude-skills · Productivity · same category
find-skills
kimyx0207/findskill · Productivity · same category
prd-to-plan
mattpocock/skills · Productivity · same category
reverse-engineering-tools
gmh5225/awesome-game-security · Productivity · same category
flutter-performance
flutter/skills · Productivity · same category
sadd:do-in-parallel fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added sadd:do-in-parallel from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: sadd:do-in-parallel is focused, and the summary matches what you get after install.
Solid pick for teams standardizing on skills: sadd:do-in-parallel is focused, and the summary matches what you get after install.
I recommend sadd:do-in-parallel for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added sadd:do-in-parallel from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
sadd:do-in-parallel reduced setup friction for our internal harness; good balance of opinion and flexibility.
sadd:do-in-parallel has been reliable in day-to-day use. Documentation quality is above average for community skills.
sadd:do-in-parallel fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for sadd:do-in-parallel matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 25