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.

Detected Capabilities

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

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