Create Github Issues Feature From Implementation Plan
Turn an approved implementation plan file into one GitHub issue per phase using repo issue templates and duplicate checks before coding starts.
Overview
create-github-issues-feature-from-implementation-plan is an agent skill most often used in Build (also Validate) that converts implementation plan phases into deduplicated GitHub issues from repo templates.
Install
npx skills add https://github.com/github/awesome-copilot --skill create-github-issues-feature-from-implementation-planWhat is this skill?
- Analyzes a plan file and emits one issue per implementation phase
- search_issues guardrail before create_issue or update_issue
- feature_request.yml or chore_request.yml templates with sensible label defaults
- Structured titles and descriptions scoped strictly to plan-required changes
- Four-step process: analyze phases, dedupe issues, create or update, template selection
- One GitHub issue required per implementation phase
- Four-step documented process from plan analysis through templated issue creation
Adoption & trust: 8.7k installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a detailed implementation plan but no phased GitHub issues, so agents and future-you cannot track what shipped per milestone.
Who is it for?
Solo builders who keep implementation plans in markdown and want GitHub as the single source of execution truth.
Skip if: Teams without GitHub or when issues are already created and linked to the same plan phases.
When should I use this skill?
Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.
What do I get? / Deliverables
Each plan phase becomes a verified GitHub issue with template-backed description and labels, ready for branch-per-issue implementation.
- One issue per plan phase with structured title and body
- Deduped backlog aligned to the plan
- Appropriate feature or chore labels applied
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Primary shelf is Build/PM because the skill operationalizes a plan into trackable GitHub work items—the handoff from planning artifact to execution backlog. PM subphase fits issue creation, phase titling, and backlog hygiene rather than writing application code.
Where it fits
Right after scope is locked in a plan file, generate one issue per phase so validation deliverables map to trackable GitHub work.
Before the first feature branch, seed the repo with phased issues agents can reference in PR descriptions.
Split a backend rollout plan into chore issues so database and API phases do not collapse into a single vague ticket.
Convert a launch checklist plan into labeled issues for release tasks without rewriting the plan in Slack.
How it compares
Use instead of manually copy-pasting plan bullets into issues; it is a GitHub workflow skill, not a code generator.
Common Questions / FAQ
Who is create-github-issues-feature-from-implementation-plan for?
Indie developers using agent tools with GitHub MCP or Copilot issue actions who standardize plan-to-backlog conversion.
When should I use create-github-issues-feature-from-implementation-plan?
After Validate when a plan file is ready—before Build coding—to seed PM tracking; also when rebasing a stale backlog against an updated multi-phase plan.
Is create-github-issues-feature-from-implementation-plan safe to install?
It instructs agents to create or update remote issues; review the Security Audits panel on this Prism page and limit repo tokens before enabling automated issue writes.
SKILL.md
READMESKILL.md - Create Github Issues Feature From Implementation Plan
# 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)