Start a fresh conversation. Replace the highlighted placeholders.
Use create-github-issues-for-unmet-specification-requirements to review [specification file] against [repository], check for partial implementations and duplicate issues, then—only after I explicitly confirm the destination and scope—create one issue per unmet requirement with requirement mapping, acceptance criteria, guidance, and appropriate labels.
Required inputs
[specification file]
[repository]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: create-github-issues-for-unmet-specification-requirementsdescription: '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
Analyze specification file to extract all requirements
Check codebase implementation status for each requirement
Search existing issues using search_issues to avoid duplicates
Create new issue per unimplemented requirement using create_issue
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
create-github-issues-for-unmet-specification-requirements by github · The Skill Leaderboard