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

Create GitHub Issues from phases in an implementation plan file.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/Cripacx/agentic-dotnet --skill create-github-issues-feature-from-implementation-plan-cripacx
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/Cripacx/agentic-dotnet/tree/main/skills/create-github-issues-feature-from-implementation-plan
Command: npx skills add https://github.com/Cripacx/agentic-dotnet --skill create-github-issues-feature-from-implementation-plan-cripacx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of GitHub Issues directly from an implementation plan, ensuring that development tasks are properly tracked and managed.

Core Features & Use Cases

  • Automated Issue Creation: Generates GitHub Issues for each phase defined in an implementation plan file.
  • Issue Tracking: Checks for existing issues to prevent duplicates and updates them if necessary.
  • Use Case: After creating a detailed implementation plan for a new feature, use this Skill to automatically create corresponding GitHub Issues for each step, streamlining the development workflow.

Quick Start

Use the create-github-issues-feature-from-implementation-plan skill to create GitHub Issues from the file named 'implementation_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 the plan file, searching for existing issues to prevent duplicates, and generating or updating one issue per phase using specified templates.

How does automated issue tracking prevent duplicate GitHub Issues when generating tasks from a plan?

Automated issue tracking prevents duplicates by searching for existing issues using the search_issues function before creating new ones, updating current issues instead of generating redundant entries.

Can I use an implementation plan file to generate GitHub Issues for each development phase?

Yes, you can use an implementation plan file to generate GitHub Issues. The process analyzes defined phases and creates a separate issue for each step to streamline task automation.

What is the best way to structure an implementation plan for automated GitHub Issue creation?

The best way to structure an implementation plan is to divide it into clear phases, allowing the automation to parse each step, verify existing issues, and generate issues with specific titles and descriptions.

Do I need existing GitHub Issues before running implementation plan task automation?

No, you do not need existing issues beforehand. The automation checks current issues via search_issues and creates new ones for untracked phases or updates existing ones if duplicates are found.

Why does my implementation plan fail to update existing GitHub Issues during automated task creation?

Implementation plan updates fail when the automation cannot match plan phases with existing issues, requiring clear phase titles and descriptions for the update_issue function to verify and apply changes.