analyze-issue

Fetch a GitHub issue and generate a structured implementation specification.

1|Updated Apr 17, 2026

Search Tags:#automation #planning #github #spec #issue #analyze

Ready to run

npx skills add https://github.com/justincordova/agents --skill analyze-issue-justincordova

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analyze-issue
Source: https://github.com/justincordova/agents/tree/main/skills/analyze-issue
Command: npx skills add https://github.com/justincordova/agents --skill analyze-issue-justincordova

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill fetches GitHub issue details, interprets context from discussions, and produces a structured implementation specification to drive planning and execution.

Core Features & Use Cases

Fetch issue data (title, body, labels, assignees, comments) from GitHub.
Analyze requirements, scope, constraints, edge cases, and dependencies across the issue discussion.
Output a ready-to-use docs/issues/<number>-<slug>.md specification for planning and delivery.

Quick Start

Analyze issue #123 in owner/repo to generate a complete implementation specification.

Frequently Asked Questions about analyze-issue

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

FAQPage Schema

How do I generate an implementation spec from a GitHub issue?▼

To generate an implementation spec from a GitHub issue, fetch the issue details including comments and labels, analyze the requirements, and output a structured markdown file with acceptance criteria and edge cases.

What is the best way to turn GitHub issue discussions into actionable requirements?▼

Turning GitHub issue discussions into actionable requirements involves interpreting the conversation context, extracting constraints and dependencies, and producing a ready-to-use specification document for delivery planning.

Can I analyze issue dependencies and scope using GitHub issue numbers?▼

Yes, you can analyze issue dependencies and scope by referencing a GitHub issue number, retrieving its full context, and mapping the affected areas and edge cases into a structured specification.

How to create a fix plan from a GitHub issue for software engineering planning?▼

Creating a fix plan from a GitHub issue requires fetching the issue data, interpreting the problem and constraints, and outputting a structured implementation specification with problem details, approach, and acceptance criteria.

Does issue analysis work with existing GitHub labels and assignees?▼

Yes, issue analysis works with existing GitHub labels and assignees by fetching these metadata fields alongside the issue body and comments to interpret the full context and requirements for the specification.

What format does the generated issue specification use?▼

The generated issue specification uses a markdown format saved as docs/issues/<number>-<slug>.md, containing structured sections for problem, requirements, affected areas, approach, edge cases, and acceptance criteria.