Create GitHub issues from specification files using the feature_request.yml template.
Works with
Analyzes specification files to extract requirements and automatically generates issue titles and descriptions
Searches existing issues to prevent duplicates before creating new ones
Supports both creating new issues and updating existing ones via the GitHub API
Applies feature and enhancement labels automatically based on specification content
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncreate-github-issue-feature-from-specificationExecute the skills CLI command in your project's root directory to begin installation:
Fetches create-github-issue-feature-from-specification from github/awesome-copilot 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:
Restart Cursor to activate create-github-issue-feature-from-specification. Access via /create-github-issue-feature-from-specification in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
0
total installs
0
this week
28.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
28.7K
stars
1e:["$","div",null,{"className":"prose prose-invert max-w-none prose-headings:font-semibold prose-headings:tracking-tight prose-h1:text-4xl prose-h1:mb-2 prose-h2:text-2xl prose-h2:mb-2 prose-h3:text-lg prose-h3:mb-2 prose-p:text-muted-foreground prose-li:text-muted-foreground prose-code:bg-muted prose-code:text-foreground prose-code:px-1 prose-code:py-0.5 prose-code:rounded-sm prose-code:text-sm prose-code:before:content-none prose-code:after:content-none prose-pre:bg-muted prose-pre:text-foreground prose-pre:border prose-pre:border-border prose-pre:rounded-md [&_table]:!border-[color:var(--border)] [&_th]:!border-[color:var(--border)] [&_td]:!border-[color:var(--border)]","dangerouslySetInnerHTML":{"__html":"<h1>Create GitHub Issue from Specification</h1>\n<p>Create GitHub Issue for the specification at <code>${file}</code>.</p>\n<h2>Process</h2>\n<ol>\n<li>Analyze specification file to extract requirements</li>\n<li>Check existing issues using <code>search_issues</code></li>\n<li>Create new issue using <code>create_issue</code> or update existing with <code>update_issue</code></li>\n<li>Use <code>feature_request.yml</code> template (fallback to default)</li>\n</ol>\n<h2>Requirements</h2>\n<ul>\n<li>Single issue for the complete specification</li>\n<li>Clear title identifying the specification</li>\n<li>Include only changes required by the specification</li>\n<li>Verify against existing issues before creation</li>\n</ul>\n<h2>Issue Content</h2>\n<ul>\n<li>Title: Feature name from specification</li>\n<li>Description: Problem statement, proposed solution, and context</li>\n<li>Labels: feature, enhancement (as appropriate)</li>\n</ul>"}}]
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
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.
github/awesome-copilot
github/awesome-copilot
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
We added create-github-issue-feature-from-specification from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: create-github-issue-feature-from-specification is focused, and the summary matches what you get after install.
Registry listing for create-github-issue-feature-from-specification matched our evaluation — installs cleanly and behaves as described in the markdown.
We added create-github-issue-feature-from-specification from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
create-github-issue-feature-from-specification reduced setup friction for our internal harness; good balance of opinion and flexibility.
create-github-issue-feature-from-specification reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: create-github-issue-feature-from-specification is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: create-github-issue-feature-from-specification is the kind of skill you can hand to a new teammate without a long onboarding doc.
create-github-issue-feature-from-specification has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend create-github-issue-feature-from-specification for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 57