Official GitHub Spec-Kit integration providing a 7-phase constitution-driven workflow for feature development.
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 feiskyer/claude-code-settings --skill spec-kit-skillCompatible with
Supported agents
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionspec-kit-skillExecute the skills CLI command in your project's root directory to begin installation:
epx add feiskyer/claude-code-settings --skill spec-kit-skillFetches spec-kit-skill from feiskyer/claude-code-settings 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/spec-kit-skill
Restart Cursor to activate spec-kit-skill. Access via /spec-kit-skillin 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.
write-a-skill
mattpocock/skills · Productivity · tag: skill
nutritional-specialist
ailabs-393/ai-labs-claude-skills · Productivity · same category
travel-planner
ailabs-393/ai-labs-claude-skills · Productivity · same category
nestjs-best-practices
kadajett/agent-nestjs-skills · Productivity · same category
pagespeed-insights
enderpuentes/ai-agent-skills · Productivity · same category
prd-to-plan
mattpocock/skills · Productivity · same category
spec-kit-skill fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: spec-kit-skill is the kind of skill you can hand to a new teammate without a long onboarding doc.
spec-kit-skill has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: spec-kit-skill is focused, and the summary matches what you get after install.
spec-kit-skill is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
spec-kit-skill has been reliable in day-to-day use. Documentation quality is above average for community skills.
spec-kit-skill reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: spec-kit-skill is focused, and the summary matches what you get after install.
Registry listing for spec-kit-skill matched our evaluation — installs cleanly and behaves as described in the markdown.
We added spec-kit-skill from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 61