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

To create GitHub issues for unmet specification requirements, the skill extracts requirement IDs from your spec file, verifies implementation status in the codebase, and generates one feature request issue per missing requirement. It prevents duplicates by searching existing issues before creating new ones.

The best way to track specification gaps is to run an automated gap analysis that extracts requirement IDs from your spec file, verifies their implementation status in the codebase, and creates templated GitHub issues for each unmet requirement to ensure missing work is tracked.

Yes, the gap analysis process checks for duplicate issues before creating new ones. It searches existing GitHub issues to verify that a feature request for a specific unmet requirement does not already exist, ensuring only truly missing work receives a new issue.

You can automate sprint planning from a specification file by running this skill against your spec. It parses the file for requirement IDs, checks the codebase for implementation status, and automatically generates GitHub feature request issues with implementation guidance for every unmet requirement.

Yes, you can use a feature request template when generating issues for missing requirements. The skill creates one templated feature request per unmet specification requirement, adding structured implementation guidance and acceptance criteria to ensure actionable sprint planning.

The limitation of automated implementation tracking is that it relies on searching the codebase for signs of partial or complete implementation to avoid false positives. Complex or non-standard implementations might be missed during the verification phase, leading to inaccurate gap analysis results.