Create Github Issues For Unmet Specification Requirements
Turn unimplemented spec requirements into deduplicated GitHub issues with acceptance criteria so your backlog matches the specification.
Overview
Create GitHub Issues for Unmet Specification Requirements is an agent skill most often used in Build (also Validate scope) that compares a specification file to the codebase and opens one GitHub issue per unimplemented r
Install
npx skills add https://github.com/github/awesome-copilot --skill create-github-issues-for-unmet-specification-requirementsWhat is this skill?
- Extracts every requirement from a specification file at a given path
- Searches the codebase and `/spec/` for partial implementation before opening issues
- Uses `search_issues` to avoid duplicate GitHub issues
- Creates one issue per unmet requirement via `create_issue` with `feature_request.yml` template
- Issue titles use requirement IDs; bodies include implementation guidance and acceptance criteria
- One GitHub issue per unimplemented requirement
- 5-step process: analyze spec, check code, search issues, create issue, use feature_request.yml
Adoption & trust: 8.6k installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your spec lists requirements but GitHub has no structured backlog entries tying each gap to implementation guidance and acceptance criteria.
Who is it for?
Maintainers with a written spec in-repo who want automated gap-to-issue sync before a sprint or agent implementation pass.
Skip if: Greenfield repos with no specification file, or teams that want a single umbrella epic instead of one issue per requirement.
When should I use this skill?
You have a specification file and want GitHub issues for requirements not yet implemented in the codebase.
What do I get? / Deliverables
After the run you get deduplicated, templated issues—one per missing requirement—ready for prioritization and implementation in your agent workflow.
- One GitHub issue per unmet requirement
- Labeled issues with acceptance criteria
- Deduped issue set verified against existing search
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Build/PM because the workflow compares living code to a spec file and files actionable backlog items—the core outcome is issue creation, not initial ideation. PM subphase covers backlog grooming, requirement traceability, and turning specs into trackable work items in the repo.
Where it fits
After freezing MVP scope in a spec, generate issues for every out-of-scope gap you still plan to build later.
Audit implementation against the spec before handing tasks to an coding agent.
Produce a launch checklist of spec items still missing so nothing ships untracked.
How it compares
Use instead of manually copying spec bullets into issues or ad-hoc chat lists that never hit `search_issues`.
Common Questions / FAQ
Who is create-github-issues-for-unmet-specification-requirements for?
Solo and indie builders using GitHub who document requirements in specification files and want their agent to backfill the issue tracker with traceable, non-duplicate work items.
When should I use create-github-issues-for-unmet-specification-requirements?
Use it during Build/PM when a spec is stable enough to audit, after Validate when scoping is done, or before Ship when you need a clear checklist of what still fails the spec—always with `${file}` pointing at the spec.
Is create-github-issues-for-unmet-specification-requirements safe to install?
It instructs the agent to create GitHub issues and search the repo; review the Security Audits panel on this Prism page and limit repo/issue permissions to what you trust the agent to modify.
SKILL.md
READMESKILL.md - Create Github Issues For Unmet Specification Requirements
# Create GitHub Issues for Unmet Specification Requirements Create GitHub Issues for unimplemented requirements in the specification at `${file}`. ## Process 1. Analyze specification file to extract all requirements 2. Check codebase implementation status for each requirement 3. Search existing issues using `search_issues` to avoid duplicates 4. Create new issue per unimplemented requirement using `create_issue` 5. Use `feature_request.yml` template (fallback to default) ## Requirements - One issue per unimplemented requirement from specification - Clear requirement ID and description mapping - Include implementation guidance and acceptance criteria - Verify against existing issues before creation ## Issue Content - Title: Requirement ID and brief description - Description: Detailed requirement, implementation method, and context - Labels: feature, enhancement (as appropriate) ## Implementation Check - Search codebase for related code patterns - Check related specification files in `/spec/` directory - Verify requirement isn't partially implemented