create-github-issues-feature-from-implementation-plan▌
github/awesome-copilot · updated Apr 8, 2026
Create GitHub Issues automatically from implementation plan phases.
- ›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
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>"}}]