speckit-github-issues-import

To convert a GitHub issue into a structured spec, this Skill fetches the issue's title, body, labels, and comments, then generates a spec.md file containing organized requirements, user stories, and acceptance criteria. It writes the output directly into your feature's spec directory.

Generating spec-kit specifications from bug reports is done by importing the GitHub issue data and transforming its unstructured text into a structured spec.md. This provides a reviewable template with an overview, problem statement, proposed solution, and functional requirements.

Yes, GitHub CLI authentication is required to import issues for spec generation. The Skill uses the GitHub CLI to securely fetch the JSON fields for the specified owner/repo#issue_number before parsing and writing the structured spec.md file.

Yes, you can use a short issue number format like #issue_number to import specs from your current repository. The parser accepts this shorthand for the active repo or the full owner/repo#issue_number format for any other repository.

The spec generation process links the created spec back to the original GitHub issue by writing an .issue-link metadata file. This file records the source issue reference and timestamps to ensure full traceability within the spec-kit workflow.

When transforming unstructured GitHub issue text into requirements, the Skill relies entirely on the issue's existing title, body, labels, and comments. It does not pull data from external sources, so incomplete issue descriptions will result in sparse spec.md output.