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

Creates GitHub Issues from implementation plan phases using YAML templates.

Updated Nov 21, 2025
One-click install
npx skills add https://github.com/lluppesms/dadabase.demo --skill create-github-issues-feature-from-implementation-plan-lluppesms
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/lluppesms/dadabase.demo/tree/main/.github/skills/create-github-issues-feature-from-implementation-plan
Command: npx skills add https://github.com/lluppesms/dadabase.demo --skill create-github-issues-feature-from-implementation-plan-lluppesms

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of GitHub Issues based on defined phases in an implementation plan, ensuring that development tasks are clearly tracked and managed.

Core Features & Use Cases

  • Automated Issue Creation: Generates GitHub Issues for each phase of an implementation plan.
  • Duplicate Prevention: Checks for existing issues before creating new ones.
  • Template Utilization: Uses predefined YAML templates (feature_request.yml or chore_request.yml) for consistent issue formatting.
  • Use Case: When a new feature is planned, this Skill can automatically create a GitHub Issue for each development phase outlined in the plan, 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 automatically create GitHub Issues from an implementation plan?

You can create GitHub Issues from an implementation plan by analyzing phase details and generating issues using predefined YAML templates. This automated issue creation ensures structured task management and prevents duplicate issue creation within a GitHub repository.

Does this automated GitHub issue creation tool prevent duplicate issues?

Yes, automated GitHub issue creation prevents duplicate issues by searching for existing issues before creating new ones. If a matching issue is found, it updates the existing issue with phase-specific details instead of generating a new entry.

What templates are used for generating GitHub Issues from a plan?

Generating GitHub Issues from a plan uses predefined YAML templates, specifically `feature_request.yml` or `chore_request.yml`. These templates ensure consistent issue formatting by populating phase-specific details and applying relevant labels during creation.

Can I update existing GitHub Issues instead of creating new ones during automation?

Yes, you can update existing GitHub Issues instead of creating new ones. The automation checks for existing issues matching the implementation plan phases and updates their phase-specific details rather than generating duplicates.

What format should the implementation plan file be in to create GitHub Issues?

The implementation plan file should be a structured markdown file, such as `plan.md`, containing defined development phases. The automation analyzes this plan file to extract phase-specific details needed to populate the GitHub Issues.