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

The Skill automates creating GitHub issues by analyzing your implementation plan to identify discrete phases. It generates a dedicated issue for each phase using feature_request.yml or chore_request.yml templates to structure the descriptions, enabling teams to track progress and ownership.

The best way to track implementation plan phases in GitHub issue tracking is to translate each phase into a dedicated issue. This automation applies template-driven descriptions to ensure per-phase issue content remains consistent and trackable.

Yes, the GitHub issue generation process performs pre-create checks for existing issues. It uses search_issues to find existing entries and will update them with update_issue or create new ones with create_issue accordingly to prevent duplicates.

You can use feature_request.yml or chore_request.yml templates when generating tasks from a phased plan. If these templates are missing, the GitHub issue generation falls back to a default format to ensure the issue is still created.

If you run GitHub issue automation on a plan without templates, the process applies a default fallback to generate the issue content. This ensures that per-phase issue creation continues even when feature_request.yml or chore_request.yml are missing.