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

Create GitHub Issues from implementation plan phases using YAML templates.

1|Updated Dec 22, 2025
One-click install
npx skills add https://github.com/dhar174/langgraph_system_generator --skill create-github-issues-feature-from-implementation-plan
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/dhar174/langgraph_system_generator/tree/main/.github/skills/create-github-issues-feature-from-implementation-plan
Command: npx skills add https://github.com/dhar174/langgraph_system_generator --skill create-github-issues-feature-from-implementation-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of translating implementation plans into actionable GitHub Issues, ensuring that development tasks are clearly defined and tracked.

Core Features & Use Cases

  • Automated Issue Creation: Generates GitHub Issues directly from phases defined in an implementation plan file.
  • Duplicate Prevention: Checks for existing issues before creating new ones, preventing redundancy.
  • Template Utilization: Leverages feature_request.yml or chore_request.yml for consistent issue formatting.
  • Use Case: After a project manager outlines a new feature's implementation phases in a plan file, this Skill can automatically create a GitHub Issue for each phase, complete with relevant details and labels.

Quick Start

Use the create-github-issues-feature-from-implementation-plan skill to create GitHub Issues from the implementation plan file named 'plan.md'.

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 create GitHub Issues from an implementation plan automatically?

To create GitHub Issues from an implementation plan, this Skill parses plan files and analyzes phases to generate issues via API calls. It uses predefined YAML templates for feature and chore requests to ensure consistent formatting and task tracking.

Can I generate GitHub Issues from a markdown plan file without creating duplicates?

Yes, you can generate GitHub Issues from a plan file without duplicates because the Skill searches for existing issues before creating new ones. If a matching issue is found, it updates the existing issue instead of creating a redundant one.

Does creating GitHub Issues from implementation plans require a specific template format?

Creating GitHub Issues from implementation plans requires using predefined YAML templates, specifically feature_request.yml or chore_request.yml. The Skill leverages these templates to format feature and chore requests consistently when making API calls.

What is the best way to track project phases in GitHub from a plan file?

The best way to track project phases in GitHub from a plan file is using an automation Skill that translates implementation plan phases into actionable GitHub Issues. It analyzes the plan and uses API calls to manage task tracking directly.

How do GitHub API calls work when generating issues from implementation plans?

GitHub API calls for generating issues from implementation plans work by parsing the plan file to extract phases, then sending requests to create or update issues. The Skill handles API integration to manage issue creation and updates automatically.

Why should I use YAML templates for GitHub Issue creation from plan files?

You should use YAML templates for GitHub Issue creation to maintain consistent issue formatting across feature and chore requests. The Skill utilizes predefined YAML templates to structure the issues generated from your implementation plan phases.