expert-driven
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 gocallum/nextjs16-agent-skills --skill expert-drivenCompatible with
Supported agents
No content available.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionexpert-drivenExecute the skills CLI command in your project's root directory to begin installation:
epx add gocallum/nextjs16-agent-skills --skill expert-drivenFetches expert-driven from gocallum/nextjs16-agent-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/expert-driven
Restart Cursor to activate expert-driven. Access via /expert-drivenin 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.
nestjs-expert
jeffallan/claude-skills · Productivity · tag: expert
powershell-7-expert
404kidwiz/claude-supercode-skills · Productivity · tag: expert
antigravity-design-expert
sickn33/antigravity-awesome-skills · Frontend · tag: expert
interior-design-expert
erichowens/some_claude_skills · Frontend · tag: expert
python-expert-best-practices-code-review
wispbit-ai/skills · Backend · tag: expert
nutritional-specialist
ailabs-393/ai-labs-claude-skills · Productivity · same category
expert-driven reduced setup friction for our internal harness; good balance of opinion and flexibility.
expert-driven is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: expert-driven is focused, and the summary matches what you get after install.
expert-driven has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: expert-driven is focused, and the summary matches what you get after install.
Useful defaults in expert-driven — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: expert-driven is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend expert-driven for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for expert-driven matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in expert-driven — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 62