Skip to content
Back to skills

Create Github Issues For Unmet Specification Requirements

ASecurity

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

  • 38,521 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added June 6, 2026
ai-agentsgit

Security analysis

A100/100

Scanned June 6, 2026

npx -y skills add github/awesome-copilot --skill create-github-issues-for-unmet-specification-requirements --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Create Github Issues For Unmet Specification Requirements?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Create Github Issues For Unmet Specification Requirements
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/github-create-github-issues-for-unmet-specification-requi/badge)](https://www.skillsdirectory.com/skills/github-create-github-issues-for-unmet-specification-requi)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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

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

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…