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

Create GitHub issues per phase from an implementation plan.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/afonsoft/VideoChat --skill create-github-issues-feature-from-implementation-plan-afonsoft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-github-issues-feature-from-implementation-plan
Source: https://github.com/afonsoft/VideoChat/tree/main/.agents/skills/create-github-issues-feature-from-implementation-plan
Command: npx skills add https://github.com/afonsoft/VideoChat --skill create-github-issues-feature-from-implementation-plan-afonsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates turning a phased implementation plan into a set of GitHub issues, one per phase, making planning traceable and actionable.

Core Features & Use Cases

  • Per-phase issue generation using the implementation plan as source of truth.
  • Template-based issue creation using feature_request.yml or chore_request.yml to ensure consistency.
  • Update existing issues when plans change, and avoid duplicates by pre-checking with search_issues.

Quick Start

Use this skill to generate GitHub issues from your implementation plan by providing the path to the plan file.

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

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate creating GitHub issues from an implementation plan?

Automating GitHub issue creation from an implementation plan involves parsing phased work streams and generating a traceable issue per phase. This skill uses your plan file as the source of truth to action each phase into a trackable GitHub issue.

Does this issue generation tool support custom GitHub issue templates?

Yes, issue generation supports custom templates by applying feature_request.yml or chore_request.yml formats. If these specific templates are unavailable, the skill defaults to standard issue creation to maintain project tracking consistency.

What is the best way to avoid duplicate GitHub issues when plans change?

To avoid duplicate GitHub issues when plans change, the system pre-checks existing issues using search_issues before creation. It updates existing issues automatically, ensuring your project management tracking remains accurate without duplicating phased tasks.

Can I update existing GitHub issues automatically when my implementation plan evolves?

You can update existing GitHub issues automatically by re-running the generation process against your modified implementation plan. The skill detects plan changes and updates the corresponding phase issues to keep project tracking perfectly synchronized.

How does phased issue creation work for software project management?

Phased issue creation for software project management works by breaking down an implementation plan into individual work streams and generating a single GitHub issue per phase. This enforces traceable task tracking and makes project phases actionable.

Do I need a specific file format to generate GitHub issues from my implementation plan?

You need to provide the file path to your existing implementation plan document. The skill reads this plan file to identify phased work streams and automatically structures them into corresponding GitHub issues for project tracking.