PluginBench
Skill
Official
Review
Audit score 70

create-github-issues-feature-from-implementation-plan

github/awesome-copilot

Turn implementation plan phases into properly templated, deduplicated GitHub Issues automatically.

What is create-github-issues-feature-from-implementation-plan?

This skill converts an implementation plan into GitHub Issues by analyzing the plan's phases and creating or updating one issue per phase. It checks for existing issues first and applies feature_request.yml or chore_request.yml templates when available, falling back to the default.

  • Analyzes an implementation plan file to identify distinct phases
  • Searches existing GitHub issues to detect duplicates
  • Creates one new issue per phase with structured title and description
  • Updates existing issues instead of duplicating when a match is found
  • Applies feature_request.yml or chore_request.yml templates, with default fallback
  • Assigns appropriate labels based on issue type (feature/chore)

How to install create-github-issues-feature-from-implementation-plan

npx skills add https://github.com/github/awesome-copilot --skill create-github-issues-feature-from-implementation-plan
Prerequisites
  • An implementation plan file with clearly defined phases
  • Access to a GitHub repository's issue tools (search_issues, create_issue, update_issue)
  • Optional: feature_request.yml or chore_request.yml issue templates configured in the repo
Claude Code
Cursor
Windsurf
Cline

How to use create-github-issues-feature-from-implementation-plan

  1. 1.Provide the path to an implementation plan file (the ${file} variable) to the agent
  2. 2.The agent analyzes the plan to identify distinct implementation phases
  3. 3.The agent searches existing GitHub issues to avoid duplicates
  4. 4.The agent creates one new issue per phase using feature_request.yml or chore_request.yml (or default template), or updates an existing matching issue
  5. 5.Review the created/updated issues for correct titles, descriptions, and labels

Use cases

Good for
  • Breaking a multi-phase implementation plan into trackable GitHub Issues
  • Bootstrapping a project's issue tracker from a design/planning document
  • Keeping GitHub issues in sync as an implementation plan evolves
  • Standardizing issue creation using feature_request.yml or chore_request.yml templates
Who it's for
  • Developers using GitHub Copilot/coding agents to manage project planning
  • Engineering leads breaking down implementation plans into actionable tickets
  • Teams that want consistent, templated GitHub issue creation from planning docs

create-github-issues-feature-from-implementation-plan FAQ

Does this skill modify the implementation plan file?

No, it only reads the plan to identify phases; it does not edit the plan file itself.

What if a matching issue already exists?

The skill checks existing issues with search_issues and updates them with update_issue instead of creating duplicates.

What issue templates does it use?

It uses feature_request.yml or chore_request.yml templates, falling back to the default GitHub issue template if neither is available.

Does it require GitHub access?

Yes, it relies on GitHub issue tools (search_issues, create_issue, update_issue) so the agent must have access to the target GitHub repository.

Full instructions (SKILL.md)

Source of truth, from github/awesome-copilot.


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

  1. Analyze plan file to identify phases
  2. Check existing issues using search_issues
  3. Create new issue per phase using create_issue or update existing with update_issue
  4. Use feature_request.yml or chore_request.yml templates (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)