> **create-github-issues-for-unmet-specification-requirements** — skill 104 of 200 in [github/awesome-copilot](https://skillsdocs.com/github/awesome-copilot).
>
> Book (all skills, one file): https://skillsdocs.com/github/awesome-copilot.md
> Machine manifest: https://skillsdocs.com/github/awesome-copilot/.well-known/agent-skills/index.json
> Install the book: `npx skills add github/awesome-copilot`
> Upstream: https://github.com/github/awesome-copilot/blob/main/skills/create-github-issues-for-unmet-specification-requirements/SKILL.md @ `main`
> Raw bytes, no header: https://raw.githubusercontent.com/github/awesome-copilot/main/skills/create-github-issues-for-unmet-specification-requirements/SKILL.md
> Base for relative paths: https://raw.githubusercontent.com/github/awesome-copilot/main/skills/create-github-issues-for-unmet-specification-requirements/
> Licence: MIT — https://spdx.org/licenses/MIT.html
>
> Content © its authors, served unmodified. Takedown: https://github.com/DreambaseAI/skillsdocs/issues/new?labels=takedown&title=Takedown+request

<!-- Verbatim upstream SKILL.md follows, YAML frontmatter included. -->

---
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