issue-to-spec

Convert GitHub issues into planning-ready specs with acceptance criteria.

Updated Mar 19, 2026

Search Tags:#workflow #planning #github #requirements #spec #issue

Ready to run

npx skills add https://github.com/japurcell/skills --skill issue-to-spec-japurcell

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-to-spec
Source: https://github.com/japurcell/skills/tree/main/skills/issue-to-spec
Command: npx skills add https://github.com/japurcell/skills --skill issue-to-spec-japurcell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converting scattered issue context (title, body, labels, comments) into a clean, planning-ready spec and checklist to guide implementation.

Core Features & Use Cases

Aggregate issue data: title, body, labels, milestone, state, assignees, and all comments.
Distill requirements, constraints, and open questions into a structured brief.
Hand off to create-spec to generate a concrete spec and acceptance criteria.
Return output paths, readiness status, and source reference to the original issue.

Quick Start

Provide an issue number and repository (owner/repo) to generate a complete feature spec and checklist.

Frequently Asked Questions about issue-to-spec

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

FAQPage Schema

How do I convert GitHub issues into planning-ready specs and requirements?▼

To generate a feature spec from a GitHub issue, provide the issue number and repository (owner/repo) to retrieve issue context via gh and produce a complete spec with acceptance criteria and a checklist.

What is the best way to aggregate GitHub issue comments into a structured brief?▼

Aggregating GitHub issue comments into a structured brief involves extracting title, body, labels, milestone, state, assignees, and comments, then distilling them into requirements, constraints, and open questions.

Does issue-to-spec work with issues across multiple GitHub projects?▼

Yes, issue-to-spec works with issues across projects by retrieving context via the gh CLI, generating PRD-style requirements and planning input that include constraints, acceptance criteria, and open questions.

Do I need the GitHub CLI installed to generate specs from GitHub issues?▼

Yes, the GitHub CLI (gh) is needed for issue retrieval, as the Skill uses it to fetch issue data before creating a structured brief and invoking create-spec to generate the final output file paths.

Can I generate acceptance criteria and open questions directly from GitHub issue context?▼

Yes, you can generate acceptance criteria and open questions directly from GitHub issue context by aggregating issue data and handing off to create-spec to produce a concrete spec and checklist.

What are the limitations of automated GitHub issue planning and spec generation?▼

Automated GitHub issue spec generation relies on existing issue context and comments, meaning poorly documented issues will yield incomplete specs, and it requires the gh CLI for issue retrieval to function correctly.