spec-from-issue

Generate a speckit specification from a GitHub issue via speckit.specify.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/refactory-lang/refactory-template --skill spec-from-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-from-issue
Source: https://github.com/refactory-lang/refactory-template/tree/main/.claude/skills/spec-from-issue
Command: npx skills add https://github.com/refactory-lang/refactory-template --skill spec-from-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of converting GitHub issues into structured specifications, bridging the gap between problem reporting and solution design.

Core Features & Use Cases

  • Automated Spec Generation: Transforms GitHub issues into speckit.specify compatible formats.
  • Contextual Extraction: Intelligently pulls relevant details like feature descriptions, scope, and success criteria from issue content.
  • Workflow Integration: Automatically updates issue labels and comments upon successful spec creation.
  • Use Case: When a new feature request comes in as a GitHub issue labeled 'spec-ready', this Skill can automatically draft the initial specification, ready for review.

Quick Start

Use the spec-from-issue skill to create a speckit specification from the GitHub issue at https://github.com/org/repo/issues/123.

Frequently Asked Questions about spec-from-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a specification from a GitHub issue?

Yes, this Skill automates converting GitHub issues into structured specifications by extracting relevant details and invoking the speckit.specify command to produce a ready-to-review specification document.

How do I automate spec creation when a new feature request comes in as a GitHub issue?

This Skill automates spec creation by fetching the GitHub issue content, intelligently extracting relevant details, and invoking the speckit.specify command to draft the initial specification ready for review.

Do I need the GitHub CLI to create speckit specifications from issue tracking data?

Yes, the GitHub CLI is required because this Skill integrates with it to fetch issue content and automatically updates issue labels and comments upon successful spec creation.

Does creating a spec with speckit automatically update the original GitHub issue?

Yes, creating a specification automatically updates the original GitHub issue by modifying its labels and posting comments upon successful specification generation.

What is the best way to bridge the gap between problem reporting and solution design in GitHub?

The best way is using this Skill to transform GitHub issues into structured speckit specifications, automatically extracting feature descriptions and success criteria to bridge problem reporting and solution design.

What details are extracted when converting a GitHub issue into a speckit specification?

When converting a GitHub issue into a speckit specification, this Skill intelligently extracts relevant details like feature descriptions, scope, and success criteria from the issue content.