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

Create GitHub issues for each phase from an implementation plan file.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/tamago0224/kuroshio-mta --skill create-github-issues-feature-from-implementation-plan-tamago0224
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/tamago0224/kuroshio-mta/tree/main/.agents/skills/create-github-issues-feature-from-implementation-plan
Command: npx skills add https://github.com/tamago0224/kuroshio-mta --skill create-github-issues-feature-from-implementation-plan-tamago0224

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating a GitHub issue for each phase of an implementation plan is time‑consuming and prone to inconsistencies.

Core Features & Use Cases

  • Phase Detection: Parses the implementation plan file to identify distinct phases.
  • Idempotent Issue Management: Searches existing issues and creates or updates one issue per phase using the appropriate template.
  • Template Selection: Automatically picks feature_request.yml or chore_request.yml based on the phase type.

Quick Start

Generate GitHub issues for the plan file 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?

To automate GitHub issue creation from an implementation plan, this Skill parses the plan file, detects individual phases, and generates one issue per phase. It searches existing issues first to avoid duplicates and automatically selects the appropriate template for each phase.

Does this issue generation tool require specific GitHub issue templates to work?

Yes, this issue generation tool requires the presence of either `feature_request.yml` or `chore_request.yml` templates in your repository. It automatically selects the appropriate template based on the detected phase type to ensure consistent issue formatting.

How does phase detection work when parsing an implementation plan?

Phase detection works by parsing the implementation plan file to identify distinct phases. Once identified, the Skill processes each phase individually to ensure exactly one issue is created or updated per phase, preventing duplicate entries in your GitHub repository.

Can I update existing GitHub issues if I run the plan parsing again?

Yes, this Skill features idempotent issue management, meaning it searches existing issues and creates or updates one issue per phase. Running it again on the same implementation plan will update existing issues rather than creating duplicates, ensuring consistent tracking.

What is the best way to avoid duplicate issues when generating tasks from an implementation plan?

The best way to avoid duplicate issues when generating tasks from an implementation plan is to use this Skill's idempotent issue management. It searches existing GitHub issues before creating new ones, ensuring only one issue exists per identified phase.