create-github-issues-for-unmet-specification-requirements
Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template.
Profile →npx skills add github/awesome-copilot --skill create-github-issues-for-unmet-specification-requirements --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 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
- Process
- Requirements
- Issue Content
- Implementation Check
What does the create-github-issues-for-unmet-specification-requirements skill do?
Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template.
How do I install it?
Run `npx skills add github/awesome-copilot --skill create-github-issues-for-unmet-specification-requirements --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.