mcpField
C
create-github-issues-for-unmet-specification-requirements

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

github.com/githubDevelopment40.5k8.9k installsUpdated 1d ago
Repository

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

This skill checks a specification against the codebase and creates a GitHub Issue for each unmet requirement. It searches existing issues first to avoid duplicates and includes implementation guidance and acceptance criteria.

Key features

  1. 01Extract requirements from specifications
  2. 02Check implementation status in code
  3. 03Search existing issues
  4. 04Create issues for unmet requirements
  5. 05Add guidance and acceptance criteria

Use cases

  1. 01Turn missing specification features into tasks
  2. 02Avoid duplicate requirement issues

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/github/awesome-copilot --skill create-github-issues-for-unmet-specification-requirements

After installing, type/create-github-issues-for-unmet-specification-requirementsin Claude Code to confirm it loaded.

Details

From the project README

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

Comments

Markdown supported