Slash Command

/spec-from-issue

Fetches GitHub issue by number using gh CLI, formats title body and URL, then invokes speckit to generate a specification.

Git

Github

git-workflow

documentation

npx claudepluginhub mintuz/claude-plugins --plugin core

Details

Argument<issue-number>

Prompt Preview

# Spec from Issue Command

Create a specification from a GitHub issue by fetching it via gh CLI and passing it to speckit's specify command.

## Arguments

`$ARGUMENTS` - GitHub issue number (required)

## Process

### 1. Validate Input

Ensure `$ARGUMENTS` contains a valid issue number:
- Must be a positive integer
- If missing, prompt: "Please provide a GitHub issue number (e.g., `/spec-from-issue 51`)"

### 2. Fetch GitHub Issue

Use gh CLI to fetch the issue details:



Extract:
- **title** - Issue title
- **body** - Issue description/body
- **number** - Issue number
- **url** - Issue U...

Command Content

Other plugins with /spec-from-issue

/create-docs

2.7k

Fetches GitHub issue details by number using helper script and generates technical specification with implementation plan, test plan, files to modify, and success criteria.

2 tools

commands-documentation-changelogs

/analyze-issue

624

Fetches GitHub issue details and generates structured technical specification with summary, approach, implementation plan, test plan, files to modify, and success criteria.

analyze-issue

/issue-create

Creates a structured GitHub issue from current context or optional description. Checks for repo issue templates, drafts title/body with summary, behaviors, criteria, context, and notes.

5 tools

mach10

Stats

Parent Repo Stars14

Parent Repo Forks4

Last CommitJan 29, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Spec from Issue Command

Create a specification from a GitHub issue by fetching it via gh CLI and passing it to speckit's specify command.

Arguments

$ARGUMENTS - GitHub issue number (required)

Process

1. Validate Input

Ensure $ARGUMENTS contains a valid issue number:

Must be a positive integer
If missing, prompt: "Please provide a GitHub issue number (e.g., /spec-from-issue 51)"

2. Fetch GitHub Issue

Use gh CLI to fetch the issue details:

gh issue view $ARGUMENTS --json title,body,number,url

Extract:

title - Issue title
body - Issue description/body
number - Issue number
url - Issue URL

If the command fails (e.g., issue doesn't exist, not in a repo, gh not authenticated):

Show the error message
Provide helpful guidance (e.g., "Run gh auth login" or "Navigate to a git repository")

3. Format for Speckit

Prepare the content to pass to speckit:

# GitHub Issue #<number>: <title>

**Source:** <url>

## Description

<body>

4. Invoke Speckit

Call the speckit specify command with the formatted content:

/speckit.specify

<formatted content from step 3>

This will hand off to speckit's specify workflow, which will guide the user through creating a proper specification.

Examples

User: /spec-from-issue 51 Claude: Fetches issue #51, formats it, and passes to /speckit.specify

User: /spec-from-issue 123 Claude: Fetches issue #123, shows formatted content, invokes speckit

Error Handling

No issue number provided: Prompt for the issue number
Invalid issue number: Show error and ask for valid number
gh CLI error: Display the error and suggest fixes (auth, repo context, etc.)
Issue not found: Show 404 message and confirm the issue number

Notes

Requires gh CLI to be installed and authenticated
Must be run from within a git repository context
The issue body supports GitHub-flavored Markdown
Speckit will take over after receiving the formatted content