create-github-issues-feature-from-implementation-plan
Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.
Profile →npx skills add github/awesome-copilot --skill create-github-issues-feature-from-implementation-plan --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Create GitHub Issue from Implementation Plan Create GitHub Issues for the implementation plan at `${file}`. ## Process 1. Analyze plan file to identify phases 2. Check existing issues using `search_issues` 3. Create new issue per phase using `create_issue` or update existing with `update_issue` 4. 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)
- Process
- Requirements
- Issue Content
What does the create-github-issues-feature-from-implementation-plan skill do?
Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.
How do I install it?
Run `npx skills add github/awesome-copilot --skill create-github-issues-feature-from-implementation-plan --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.