Skip to content
AI & Agents
Skill

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

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

From plugin
awesome-copilot
39k200 skills200 agents
Install
$ npx -y skills add github/awesome-copilot --skill create-github-issues-for-unmet-specification-requirements --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/create-github-issues-for-unmet-specification-requirements

Context preview

The summary Claude sees to decide when to auto-load this skill.

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

SKILL.md

create-github-issues-for-unmet-specification-requirements.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
Ships withawesome-copilot

A community-created collection of custom agents, instructions, skills, hooks, workflows, and plugins to supercharge your GitHub Copilot experience.

Get the whole plugin

Other skills on awesome-copilot.