SkillsAdd

github/awesome-copilot · Official

create-github-issues-for-unmet-specification-requirements

Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template.

All-time #1734 First seen Feb 25, 2026
8-week activity · all time api

Installation

$ npx skills add github/awesome-copilot --skill create-github-issues-for-unmet-specification-requirements
View on skills.sh ↗ GitHub repository ↗

Summary

  • Automatically create GitHub issues for specification requirements not yet implemented in code.
  • Analyzes specification files to extract all requirements, then checks codebase implementation status for each one Searches existing issues to prevent duplicates before creating new feature request issues Generates issues with requirement IDs, detailed descriptions, implementation guidance, and acceptance criteria Scans related specification files and code patterns to verify whether requirements are partially or fully implemented

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic
anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from github/awesome-copilot · top by installs.

npx skills add github/awesome-copilot
git-commit 44.5K excalidraw-diagram-generator 29.1K documentation-writer 26.2K multi-stage-dockerfile 23.4K prd 22.9K gh-cli 21.9K refactor 21.6K java-springboot 19.9K create-readme 18.1K playwright-generate-test 18K

Browse all from github/awesome-copilot

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 38.8K
License LICENSE
Default branch main
Open issues 21
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents github-copilot

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,275 B
  • docs SUMMARY.md 177 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 9,000 installs

SKILL.md

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