Create Github Issue Feature From Specification
Turn an approved feature specification file into a single tracked GitHub issue using the repo’s feature_request template—without duplicating open work.
Overview
create-github-issue-feature-from-specification is an agent skill for the Build phase that creates or updates one GitHub feature issue from a specification file using the feature_request.yml template.
Install
npx skills add https://github.com/github/awesome-copilot --skill create-github-issue-feature-from-specificationWhat is this skill?
- 4-step process: analyze spec, search_issues, create_issue or update_issue, apply feature_request.yml
- One issue per complete specification with scope limited to spec-required changes
- Mandatory duplicate check before create
- Issue body covers problem, proposed solution, and context with feature/enhancement labels
- 4-step documented process from spec analysis through issue create or update
Adoption & trust: 8.6k installs on skills.sh; 34.6k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a feature spec on disk but no single GitHub issue that captures it, and you are not sure if someone already filed the same request.
Who is it for?
Solo builders using GitHub Issues who document features in spec files and want agent-driven backlog intake with duplicate detection.
Skip if: Repos without GitHub Issues, specs that need many separate tickets per sub-feature in one run, or non-GitHub trackers.
When should I use this skill?
You have a specification at a known path and need one GitHub feature issue filed or updated using the repo template.
What do I get? / Deliverables
A deduplicated GitHub issue exists with template-aligned title, labels, and spec-only scope—ready for assignment or breakdown into tasks.
- One GitHub issue (created or updated) scoped to the specification
- Duplicate check against existing issues documented in the run
Recommended Skills
Journey fit
Backlog hygiene sits in Build under PM: specs become actionable issues while you are still shaping what to implement. Issue creation from `${file}` is the handoff from written spec to sprint-visible work on GitHub.
How it compares
Opinionated single-issue workflow from a spec path—not a generic multi-issue epic splitter or Jira importer.
Common Questions / FAQ
Who is create-github-issue-feature-from-specification for?
Solo and indie developers who keep feature specs in files and track delivery on GitHub with standardized feature request templates.
When should I use create-github-issue-feature-from-specification?
In Build PM when a specification is ready to track, after validation scope is set, or when onboarding an agent to file work without duplicating open issues.
Is create-github-issue-feature-from-specification safe to install?
It instructs create and update actions on your repo; review the Security Audits panel on this page and confirm GitHub token scopes before enabling.
SKILL.md
READMESKILL.md - Create Github Issue Feature From Specification
# Create GitHub Issue from Specification Create GitHub Issue for the specification at `${file}`. ## Process 1. Analyze specification file to extract requirements 2. Check existing issues using `search_issues` 3. Create new issue using `create_issue` or update existing with `update_issue` 4. Use `feature_request.yml` template (fallback to default) ## Requirements - Single issue for the complete specification - Clear title identifying the specification - Include only changes required by the specification - Verify against existing issues before creation ## Issue Content - Title: Feature name from specification - Description: Problem statement, proposed solution, and context - Labels: feature, enhancement (as appropriate)