Create GitHub Issues automatically from implementation plan phases.
Works with
Analyzes implementation plan files to identify phases and generates one issue per phase
Uses feature_request.yml or chore_request.yml templates, with fallback to default issue format
Checks for existing issues before creation to avoid duplicates, and updates existing issues when needed
Includes phase details, requirements, and context in issue descriptions with appropriate labels
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncreate-github-issues-feature-from-implementation-planExecute the skills CLI command in your project's root directory to begin installation:
Fetches create-github-issues-feature-from-implementation-plan 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-issues-feature-from-implementation-plan. Access via /create-github-issues-feature-from-implementation-plan 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 Implementation Plan</h1>\n<p>Create GitHub Issues for the implementation plan at <code>${file}</code>.</p>\n<h2>Process</h2>\n<ol>\n<li>Analyze plan file to identify phases</li>\n<li>Check existing issues using <code>search_issues</code></li>\n<li>Create new issue per phase using <code>create_issue</code> or update existing with <code>update_issue</code></li>\n<li>Use <code>feature_request.yml</code> or <code>chore_request.yml</code> templates (fallback to default)</li>\n</ol>\n<h2>Requirements</h2>\n<ul>\n<li>One issue per implementation phase</li>\n<li>Clear, structured titles and descriptions</li>\n<li>Include only changes required by the plan</li>\n<li>Verify against existing issues before creation</li>\n</ul>\n<h2>Issue Content</h2>\n<ul>\n<li>Title: Phase name from implementation plan</li>\n<li>Description: Phase details, requirements, and context</li>\n<li>Labels: Appropriate for issue type (feature/chore)</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
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
Keeps context tight: create-github-issues-feature-from-implementation-plan is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added create-github-issues-feature-from-implementation-plan from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
We added create-github-issues-feature-from-implementation-plan from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
create-github-issues-feature-from-implementation-plan reduced setup friction for our internal harness; good balance of opinion and flexibility.
create-github-issues-feature-from-implementation-plan has been reliable in day-to-day use. Documentation quality is above average for community skills.
create-github-issues-feature-from-implementation-plan is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
create-github-issues-feature-from-implementation-plan reduced setup friction for our internal harness; good balance of opinion and flexibility.
create-github-issues-feature-from-implementation-plan reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added create-github-issues-feature-from-implementation-plan from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
create-github-issues-feature-from-implementation-plan is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 38