Skip to main content
affpapa.org
RU EN
skill GitHub Copilot official · GitHub

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

This skill turns implementation plan phases into GitHub Issues, checking for existing issues first. Use it when a finished plan needs to become trackable work.

Install into GitHub Copilot · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add github/awesome-copilot --skill create-github-issues-feature-from-implementation-plan
Open on GitHub

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

The skill reads the plan file at ${file}, identifies its phases, and searches existing GitHub Issues with search_issues. For each phase, it creates an issue with create_issue or updates a matching one with update_issue.

It uses feature_request.yml or chore_request.yml templates, falling back to the default template. Each issue gets the phase name, details, requirements, context, and a label suited to a feature or chore. Existing issues are checked before new ones are created.

Install it when your plan has clear phases that should become separate issues. If the plan is still vague, organize its phases first.

What it helps with

  • turn implementation plan phases into separate GitHub Issues
  • check whether a phase already has an issue
  • update a matching issue instead of creating a duplicate
  • apply a feature or chore template and label

Example prompts for the agent

  • Create GitHub Issues for the phases in `${file}`.
  • Check for existing issues and update any that match the plan phases.
  • Read `${file}` and create one issue per phase with the right label.

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

1Skills CLI (Vercel)

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

2GitHub CLI

gh skill install github/awesome-copilot create-github-issues-feature-from-implementation-plan

3Manually: put the files in place

.github/skills/create-github-issues-feature-from-implementation-plan/SKILL.md

From the same set554

The whole set →
git-commit official github This skill reviews Git changes, stages related files, and creates Conventional Commits. Use it when you want an agent to make one commit or split work into separate commits. GitHub Copilot 47,165installs excalidraw-diagram-generator official github Turn a plain-language description into an Excalidraw diagram. Useful for mapping processes, system structure, and relationships between entities. GitHub Copilot 31,639installs multi-stage-dockerfile official github This skill guides GitHub Copilot in writing multi-stage Dockerfiles for different languages and frameworks. Use it when the final runtime image should contain fewer build dependencies. GitHub Copilot 29,688installs documentation-writer official github Skill that turns the agent into a technical writer following the Diátaxis framework: tutorials, how-to guides, reference, and explanation. Proposes structure before writing. GitHub Copilot 27,757installs prd official github Turns a feature idea into a structured PRD with user stories, technical requirements, and risks. Use it when planning a software feature or an AI-powered one. GitHub Copilot 24,035installs refactor official github This skill reshapes existing code without changing its external behavior. Use it for gradual cleanup of large functions, duplication, weak types, and code smells. GitHub Copilot 22,321installs java-springboot official github Gives GitHub Copilot Spring Boot development practices, from project layout to tests and security. Use it when writing or reviewing Java application code. GitHub Copilot 21,272installs create-readme official github This skill reviews a project and creates a structured README.md. Use it when the repository needs clear documentation based on its actual files and code. GitHub Copilot 19,081installs

Similar

setup-matt-pocock-skills Matt Pocock Sets up a repository for Matt Pocock engineering skills with issue tracking, triage labels, and domain-document rules. Run it before using the other engineering skills. Claude Code 1,052,851installs triage Matt Pocock This skill moves issues and external PRs through triage states, verification, and agent briefs. It fits maintainers managing an issue queue. Claude Code 990,453installs code-review Matt Pocock Reviews changes from a chosen reference point against repository standards and the originating spec. Use it for a branch, PR, or work in progress. Claude Code 789,521installs implement Matt Pocock Implements work from a specification or tickets, following a test-driven flow and ending with review and a commit. Use it when a coding task needs a defined delivery routine. Claude Code 774,700installs git-guardrails-claude-code Matt Pocock This skill adds a Claude Code hook that stops risky Git commands before they run. Use it when an agent must not push or discard working-tree changes. Claude Code 499,069installs setup-pre-commit Matt Pocock This skill configures pre-commit checks for a JavaScript repository, running Prettier, type checking, and tests before each commit. Claude Code 489,289installs

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

How do I install create-github-issues-feature-from-implementation-plan in GitHub Copilot?

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

What does create-github-issues-feature-from-implementation-plan do?

It identifies phases in an implementation plan and creates a GitHub Issue for each, checking existing issues first.

Which issue templates does the skill use?

It uses feature_request.yml or chore_request.yml. If neither template is available, it falls back to the default.

Source text

SKILL.md · MIT 
---
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)

© github · MIT · github/awesome-copilot

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor