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

Creates GitHub Issues from implementation plan phases using feature or chore request templates.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/miyake-san/sogo-agent-platform --skill create-github-issues-feature-from-implementation-plan-miyake-san
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/miyake-san/sogo-agent-platform/tree/main/skills/core/create-github-issues-feature-from-implementation-plan
Command: npx skills add https://github.com/miyake-san/sogo-agent-platform --skill create-github-issues-feature-from-implementation-plan-miyake-san

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually translating a multi-phase implementation plan into trackable GitHub Issues is repetitive and error-prone, often leading to duplicated issues or missing phases. This Skill automates the conversion so every plan phase becomes a properly structured issue. ## Core Features & Use Cases - Phase-to-Issue Mapping: Analyzes an implementation plan file and creates one GitHub Issue per phase with clear titles and descriptions. - Duplicate Detection: Searches existing issues with search_issues before creating new ones, updating existing issues via update_issue when appropriate. - Template-Based Formatting: Uses feature_request.yml or chore_request.yml issue templates, falling back to a default structure when templates are unavailable. - Use Case: After drafting a five-phase implementation plan for a new API service, run this Skill to generate five labeled GitHub Issues ready for sprint planning. ## Quick Start Create GitHub Issues from the implementation plan in docs/plan.md, one issue per phase using the feature request template.

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?

Provide the path to your implementation plan file and the Skill analyzes it to identify phases. It then creates one GitHub Issue per phase using the create_issue tool, with titles and descriptions derived from the plan content.

How to avoid duplicate GitHub Issues when generating from a plan?

The Skill uses the search_issues tool to check for existing issues before creating new ones. When a matching issue already exists, it updates that issue with update_issue instead of creating a duplicate.

What issue templates does GitHub issue creation support?

The Skill uses the feature_request.yml template for feature phases and the chore_request.yml template for maintenance tasks. If neither template is available in the repository, it falls back to a default issue structure.

Can I generate issues for both features and chores from one plan?

Yes, the Skill selects the appropriate template based on the phase type. Feature phases use feature_request.yml while maintenance or cleanup phases use chore_request.yml, each with matching labels.

What are the limitations of automated GitHub issue creation from plans?

The Skill only includes changes explicitly required by the plan, so vague or incomplete plan files produce sparse issues. It also depends on the plan having clearly identifiable phases to map into individual issues.