Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.
v1.0LATEST
NewUpdated Jun 26, 2026
Create GitHub Issue from Implementation Plan
Create GitHub Issues for the implementation plan at ${file}.
Process
Analyze plan file to identify phases
Check existing issues using search_issues
Create new issue per phase using create_issue or update existing with update_issue
Use feature_request.yml or chore_request.yml templates (fallback to default)
Requirements
One issue per implementation phase
Clear, structured titles and descriptions
Include only changes required by the plan
Verify against existing issues before creation
Issue Content
Title: Phase name from implementation plan
Description: Phase details, requirements, and context
Labels: Appropriate for issue type (feature/chore)
Files1
1 files · 1.0 KB
Select a file to preview
Overall Score
62/100
Grade
C
Adequate
Grades are signals, not a certification. Always review a skill yourself before use.
Safety
78
Quality
55
Clarity
68
Completeness
48
Summary
This skill guides agents to create GitHub Issues from implementation plans by analyzing phase information and leveraging GitHub issue templates (feature_request.yml or chore_request.yml). The agent searches for existing issues to avoid duplicates, then creates or updates issues with structured titles, descriptions, and labels based on the plan phases.
Phrases that agents use to match this skill to user intent.
create issues from plangithub issue generationimplementation plan trackingbulk issue creationfeature request template
Use Cases
Convert implementation plan phases into actionable GitHub Issues
Bulk create feature and chore issues from a structured plan
Maintain issue deduplication by checking existing issues before creation
Apply consistent templating and labeling across related issues
Track implementation progress through structured issue organization
Quality Notes
The skill correctly emphasizes deduplication through `search_issues` before creation, reducing noise
Clear fallback strategy (feature_request.yml or chore_request.yml templates, with default fallback) provides robustness
One-issue-per-phase requirement is explicit and operationally clear
Scope is well-defined: skill operates only on implementation plan files and GitHub issues
Missing: no guidance on how to handle merge conflicts if multiple agents create issues concurrently
Missing: no error handling patterns documented (e.g., what if a template is malformed or GitHub API returns 403)
Missing: no examples of expected plan file format or output
The instruction 'Include only changes required by the plan' is somewhat vague — guidance on excluding unrelated changes would strengthen clarity
Model: claude-haiku-4-5-20251001Analyzed: Jun 26, 2026
Reviews
Add this skill to your library to leave a review.
No reviews yet
Be the first to share your experience.
Use github/create-github-issues-feature-from-implementation-plan in your dev environment — a Developer account adds skills to your library and syncs them via the SkillRepo CLI.