create-github-issues-for-unmet-specification-requirements
github/awesome-copilot
Automatically files GitHub Issues for every requirement in a spec that isn't implemented yet.
What is create-github-issues-for-unmet-specification-requirements?
This skill analyzes a specification file, determines which requirements are not yet implemented in the codebase, and automatically creates a GitHub Issue for each unmet requirement using the feature_request.yml template. It checks existing issues first to avoid duplicates, making it useful for keeping a backlog in sync with a spec document.
- Extracts all requirements from a given specification file
- Checks the codebase to determine which requirements are already implemented
- Searches existing GitHub issues to avoid duplicate issue creation
- Creates a GitHub issue per unimplemented requirement with requirement ID, description, implementation guidance, and acceptance criteria
- Applies the feature_request.yml issue template (or default template fallback) with appropriate labels
How to install create-github-issues-for-unmet-specification-requirements
npx skills add https://github.com/github/awesome-copilot --skill create-github-issues-for-unmet-specification-requirements- A specification file describing requirements (e.g., in a /spec/ directory)
- Access to GitHub Issues API/tools (search_issues, create_issue) for the target repository
- A feature_request.yml issue template (optional; default template used as fallback)
How to use create-github-issues-for-unmet-specification-requirements
- 1.Provide the path to the specification file (the ${file} variable) you want analyzed
- 2.Let the skill analyze the specification file to extract all requirements
- 3.The skill checks the codebase to determine implementation status of each requirement
- 4.The skill searches existing GitHub issues to avoid creating duplicates
- 5.Review and confirm as the skill creates one GitHub issue per unimplemented requirement using the feature_request.yml template
Use cases
- Syncing a backlog with a newly updated specification document
- Auditing a codebase against a spec to find gaps in implementation
- Generating actionable feature request issues for a development team from a requirements doc
- Preventing duplicate issue creation when re-running spec compliance checks
- Bootstrapping a project's issue tracker from an initial specification
- Engineering leads tracking spec-to-implementation gaps
- Developers maintaining specification-driven projects
- Project managers wanting an auto-generated backlog from requirements documents
- Teams using GitHub Issues for feature tracking
create-github-issues-for-unmet-specification-requirements FAQ
Yes, it uses search_issues to check existing issues before creating a new one for a requirement.
It uses the feature_request.yml issue template, falling back to the default template if that one isn't available.
Yes, it relies on tools like search_issues and create_issue, implying the agent must have GitHub access configured.
No, it checks codebase implementation status and only creates issues for unimplemented or non-partially-implemented requirements.
Full instructions (SKILL.md)
Source of truth, from github/awesome-copilot.
name: create-github-issues-for-unmet-specification-requirements description: 'Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template.'
Create GitHub Issues for Unmet Specification Requirements
Create GitHub Issues for unimplemented requirements in the specification at ${file}.
Process
- Analyze specification file to extract all requirements
- Check codebase implementation status for each requirement
- Search existing issues using
search_issuesto avoid duplicates - Create new issue per unimplemented requirement using
create_issue - Use
feature_request.ymltemplate (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
Related skills
More from github/awesome-copilot and the wider catalog.
git-commit
Execute semantic git commits with conventional message analysis and intelligent staging.
excalidraw-diagram-generator
Generate Excalidraw diagrams from natural language descriptions.
documentation-writer
Create structured technical documentation using the Diátaxis framework for tutorials, how-to guides, references, and explanations.
gh-cli
GitHub CLI comprehensive reference for repositories, issues, PRs, Actions, projects, releases, and all GitHub operations from the command line.
prd
Generate comprehensive Product Requirements Documents with executive summaries, user stories, technical specs, and risk analysis.
refactor
Surgical code refactoring to improve maintainability without changing behavior.