GitHub issues for unmet spec requirements
Turn unimplemented spec requirements into GitHub issues — requirement extraction, codebase verification, duplicate avoidance, feature_request.yml templates
- What
- Turn unimplemented spec requirements into GitHub issues — requirement extraction, codebase verification, duplicate avoidance, feature_request.yml templates
- Cost
- Free
- Needs
- an agent with GitHub issue tooling (search_issues/create_issue or equivalent) and write access to the repository; nothing else — the skill is a process, no paid accounts required for public repos
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a skill from the `github/awesome-copilot` community collection that turns unimplemented requirements in a specification file into GitHub issues: analyze the spec to extract all requirements, check each one's implementation status against the codebase (including `/spec/` directory and related code patterns), search existing issues to avoid duplicates, then create one issue per unmet requirement with a requirement ID, detailed description, implementation guidance and acceptance criteria — using the `feature_request.yml` template with a fallback to the default. By @github, listed here with credit to its creator. Honest caveats: the skill assumes an agent with issue tooling (`search_issues`/`create_issue`) and repository write access; short, process-oriented skill — no code of its own; MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: an agent with GitHub issue tooling (search_issues/create_issue or equivalent) and write access to the repository; nothing else — the skill is a process, no paid accounts required for public repos Install "GitHub issues for unmet spec requirements" for me. It gives the agent the github/awesome-copilot skill for turning unimplemented spec requirements into GitHub issues: analyze the specification file, verify each requirement's implementation status against the codebase, search existing issues to avoid duplicates, and create one issue per unmet requirement with requirement ID, description, implementation guidance and acceptance criteria using the feature_request.yml template. MIT-licensed. Repository: https://github.com/github/awesome-copilot/blob/main/skills/create-github-issues-for-unmet-specification-requirements/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "create-github-issues-for-unmet-specification-requirements". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at the specification file to analyze; confirm which repo to create issues in). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.