github/awesome-copilot · Official

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

Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.

All-time #1634 Trending #9247 First seen Feb 25, 2026
8-week activity · all time api

Installation

$ npx skills add github/awesome-copilot --skill create-github-issues-feature-from-implementation-plan

Summary

  • 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

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from github/awesome-copilot · top by installs.

npx skills add github/awesome-copilot

Browse all from github/awesome-copilot

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 38.8K
License LICENSE
Default branch main
Open issues 21
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents github-copilot

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 945 B
  • docs SUMMARY.md 171 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 9,400 installs

SKILL.md

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 createissue or update existing with updateissue
  4. Use featurerequest.yml or chorerequest.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)