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

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

This skill automates the creation of GitHub issues for requirements in a specification file that have not yet been implemented in the codebase. It solves the gap between written specs and delivered code by systematically turning unmet requirements into tracked, actionable issues, reducing the chance that documented needs are silently dropped.

The workflow is compact: analyze the specification file to extract all requirements, check the codebase to determine each requirement's implementation status, search existing issues (via search_issues) to avoid duplicates, and create one new issue per unimplemented requirement (via create_issue) using the repository's feature_request.yml template, falling back to the default template when absent. Each issue is expected to carry a clear requirement ID and description mapping, implementation guidance, and acceptance criteria, with labels like feature or enhancement as appropriate. The implementation check includes searching the codebase for related patterns, checking related spec files under a /spec/ directory, and verifying a requirement is not already partially implemented.

It targets developers, tech leads, and project maintainers who work from specification documents and want to keep their issue tracker in sync with unmet requirements. Typical use cases include bootstrapping a backlog from a new spec, reconciling a spec against an existing codebase, and ensuring each requirement has a traceable issue. This is a thin, read-and-create workflow: it reads the spec and code and writes GitHub issues through standard tooling, with no destructive operations, credential handling, or code execution, making it low risk.

FAQ

What does this skill produce?

One GitHub issue per unimplemented requirement found in the specification, each with a requirement ID and description, implementation guidance, acceptance criteria, and appropriate labels such as feature or enhancement.

How does it avoid creating duplicate issues?

Before creating issues it searches existing issues (using search_issues) and verifies each requirement is not already implemented or partially implemented in the codebase.

What issue template does it use?

It uses the repository's feature_request.yml template, and falls back to the default template if that is not available.

How does it determine whether a requirement is implemented?

It searches the codebase for related code patterns and checks related specification files under a /spec/ directory to assess implementation status.

Do I provide the specification file?

Yes. The skill operates on a specification file you point it at, extracting all requirements from it before checking implementation status.