create-github-issues-feature-from-implementation-plan
- Use it when:
- You have an implementation plan split into phases and want each phase tracked as a GitHub issue.
- It does:
- Reads the plan file, searches the existing issues, then creates an issue per phase or updates the one that already covers it.
- You get:
- GitHub issues titled with each phase's name, holding its details, requirements and context, labelled as a feature or a chore.
- Templates:
- The repo's feature_request.yml or chore_request.yml issue templates, falling back to the default one.
- Needs:
- GitHub issue tools named search_issues, create_issue and update_issue.
- Part of:
- The repo's project-planning plugin, next to create-implementation-plan.
Needs GitHub issue tools named search_issues, create_issue and update_issue, such as the GitHub MCP server provides.
TL;DR
A short command for turning a plan into tracked work. You point it at a plan file, and it splits the plan into its phases, one issue each. Before creating anything it searches the repository's issues with search_issues, so a phase that already has an issue gets that issue updated with update_issue instead of a duplicate; new ones go through create_issue. Each issue takes the phase name as its title and the phase's details, requirements and context as its description, limited to the changes the plan requires, with labels that fit a feature or a chore. It uses the feature_request.yml or chore_request.yml issue template when the repository has one, and the default template otherwise.
Summarizes the skill at 797337f.
npx skills add https://github.com/github/awesome-copilot --skill create-github-issues-feature-from-implementation-plan skills.sh pageSource on GitHubAll skills from github/awesome-copilot
- Total Downloads
- 9,500 on skills.sh, Nov 9, 2026
- Repo stars
- 40,943 github/awesome-copilot
- First seen
- Feb 25, 2026 on skills.sh
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 36 |
| Sep 28 | 31 |
| Oct 5 | 38 |
| Oct 12 | 20 |
| Oct 19 | 18 |
| Oct 26 | 23 |
| Nov 2 | 31 |
| Nov 9 | 14 |
| Category |
Make the agent question you and write the plan down before it writes code. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills. |
|---|---|
| Type |
A one-shot action you invoke by name, such as turning the conversation into a PRD. |
| Effect |
Its own steps change something outside your machine: post, send, deploy, provision, file issues, drive a website, or upload data to a service. |
| Needs |
Reads or writes an issue tracker, GitHub Issues by default. Needs an MCP server connected. |
| Publisher |
A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates. |
| Topics | |
| Stack |
SKILL.md
From github/awesome-copilot at 797337f. Checked daily, last changed Nov 6, 2026.
Frontmatter
name: create-github-issues-feature-from-implementation-plan
description: 'Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.'Create GitHub Issue from Implementation Plan
Create GitHub Issues for the implementation plan at ${file}.
Process
- Analyze plan file to identify phases
- Check existing issues using
search_issues - Create new issue per phase using
create_issueor update existing withupdate_issue - Use
feature_request.ymlorchore_request.ymltemplates (fallback to default)
Requirements
- One issue per implementation phase
- Clear, structured titles and descriptions
- Include only changes required by the plan
- Verify against existing issues before creation
Issue Content
- Title: Phase name from implementation plan
- Description: Phase details, requirements, and context
- Labels: Appropriate for issue type (feature/chore)