Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template. Use when you need help with create github issues for unmet specification requirements.
Scanned 9/8/2026
Install to Claude Code
npx -y skills add anubhavg-icpl/vibe --skill ghcopilot-create-github-issues-for-unmet-specification-requirements --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Ghcopilot Create Github Issues For Unmet Specification Requirements?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/anubhavg-icpl-ghcopilot-create-github-issues-for-unmet-specifica)More formats (shields.io, HTML) on the badges page.
---
name: create-github-issues-for-unmet-specification-requirements
description: Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template. Use when you need help with create github issues for unmet specification requirements.
license: CC-BY-NC-SA-4.0
---
# 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
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!