Index of every page on this site: llms.txt
All skills
github avatar

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

@f10fdb8 official
by githubgithub/awesome-copilot41k stars
5,399
Run it yourself

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

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/create-github-issues-feature-from-implementation-plan

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈41 tokens for metadata: the name and description. ≈188 when used: this file.

Description uses 2.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈166 characters, or 2.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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)

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

2 warnings2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill is generally safe but processes external implementation plans which could potentially contain indirect prompt injections. It uses standard GitHub tools to manage repository issues based on the content of those files.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: MEDIUM · 1 issue

  • Runlayer8mo

    1/1 file flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at f10fdb8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 7 months ago
  • github
  • issues
  • automation
  • implementation-planning
  • workflow
  • feature-request
  • templates

README badge

README badge for github/awesome-copilot/create-github-issues-feature-from-implementation-plan

Creates GitHub Issues from an implementation plan file, with one issue per phase, using feature_request.yml or chore_request.yml templates and checking for duplicates via search. Targets teams using GitHub's issue workflow to track feature development across multiple phases.

Generated from the current SKILL.md.

What file formats does this skill accept for implementation plans?
The SKILL.md does not specify supported file formats. It references analyzing a plan file at ${file} but does not document which formats (Markdown, JSON, YAML, etc.) are accepted.
Does this skill create issues based on GitHub issue templates?
Yes. The skill uses feature_request.yml or chore_request.yml templates when available, with a fallback to the default issue template.
What happens if an issue for a phase already exists?
The skill checks existing issues before creation and updates existing issues with `update_issue` rather than creating duplicates.
Does this skill assign labels to created issues?
Yes. The skill applies labels appropriate to the issue type (feature or chore) based on the phase classification.

Generated from the current SKILL.md. These answers refresh after source changes.