Interactive requirements gathering and professional PRD generation through quality-scored dialogue.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add cexll/myclaude --skill product-requirementsCompatible with
Supported agents
Systematically assesses requirements across five dimensions (business value, functional specs, UX, technical constraints, scope) using a 100-point quality scale, iterating until 90+ threshold before document generation
Gathers project context by reading existing README and configuration files, then asks targeted clarification questions focused on the lowest-scoring requirement areas
Ge
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionproduct-requirementsExecute the skills CLI command in your project's root directory to begin installation:
epx add cexll/myclaude --skill product-requirementsFetches product-requirements from cexll/myclaude 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/product-requirements
Restart Cursor to activate product-requirements. Access via /product-requirementsin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
mobile-app-ui-design
ceorkm/mobile-app-ui-design · Frontend · same category
frontend-ui-ux
code-yeongyu/oh-my-opencode · Frontend · same category
design-taste-frontend
bnd-1/taste-skill · Frontend · same category
next-best-practices
vercel-labs/next-skills · Frontend · same category
karpathy-guidelines
forrestchang/andrej-karpathy-skills · Frontend · same category
frontend-security
schalkneethling/webdev-agent-skills · Frontend · same category
Registry listing for product-requirements matched our evaluation — installs cleanly and behaves as described in the markdown.
product-requirements has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in product-requirements — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend product-requirements for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
product-requirements fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
product-requirements is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added product-requirements from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: product-requirements is the kind of skill you can hand to a new teammate without a long onboarding doc.
product-requirements has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: product-requirements is focused, and the summary matches what you get after install.
showing 1-10 of 73