Create GitHub Issue Feature From Specification

Feature specifications in documents or conversations need transformation into actionable GitHub issues with clear scope, acceptance criteria, and technical details. This skill analyzes feature requirements to generate well-structured GitHub issues including problem statements, proposed solutions, implementation tasks, and testing criteria for effective development tracking.

What Is This?

Overview

Create GitHub Issue Feature From Specification converts feature descriptions into structured GitHub issues. It extracts core requirements from specifications, formulates clear problem statements, proposes technical implementation approaches, breaks features into sub-tasks, defines acceptance criteria, suggests appropriate labels and milestones, and formats everything following GitHub issue conventions.

The skill translates business requirements into developer-actionable issues, identifies technical dependencies, surfaces questions needing clarification, and structures information enabling developers to understand requirements and begin implementation efficiently.

Who Should Use This

Product managers translating requirements to issues. Engineering managers planning feature development. Technical leads breaking down large features. Developers creating implementation tasks. Open source maintainers accepting feature requests. Teams maintaining GitHub project boards.

Why Use It?

Problems It Solves

Manual issue creation from specifications is time-consuming and inconsistent. This skill automates extraction and formatting, ensuring complete and well-structured issues.

Poorly written issues lack context, causing developers to seek clarification repeatedly. Generated issues include problem context, proposed approach, and acceptance criteria reducing ambiguity.

Breaking features into appropriately sized issues requires technical understanding. The skill suggests reasonable task breakdown based on feature complexity and common patterns, while also surfacing dependencies, edge cases, and testing requirements developers need to consider.

Core Highlights

Specification parsing and requirement extraction. Problem statement formulation. Technical approach recommendation. Task breakdown into sub-issues. Acceptance criteria definition. Label and milestone suggestions. Dependency identification and edge case consideration.

How to Use It?

Basic Usage

Provide a feature specification as text, document, or conversation summary. The skill generates GitHub issue content ready to paste or create via API.

Create GitHub issue from this feature spec:
[Paste specification]

Generate issue for adding user profile editing
with avatar upload and bio field

Specific Scenarios

For complex features, request task breakdown.

Create parent issue with sub-tasks for
implementing OAuth2 authentication flow

For API features, include technical specifications.

Create issue for new REST endpoint
including request/response schemas

Real World Examples

A product manager writes a feature specification for social sharing functionality. Using this skill, the specification is analyzed to extract requirements for sharing to Twitter, Facebook, and LinkedIn. The skill generates an issue with a problem statement about increasing content reach, proposes a technical approach using OAuth and platform APIs, breaks work into sub-tasks for OAuth integration, share button UI, and analytics tracking, defines acceptance criteria including successful post creation and error handling, and formats everything in markdown ready for GitHub. Developers can pick up the issue and implement without seeking clarification.

An engineering manager planning a large feature across multiple repositories uses the skill to process the overall specification, generate a parent tracking issue, create sub-issues for API changes, UI implementation, and database migrations, identify dependencies, and suggest milestones grouping related work. Project tracking becomes straightforward with a well-structured issue hierarchy.

A developer receiving a feature request in Slack can use the skill to analyze the chat transcript, extract concrete requirements, identify open questions needing product input, formulate a technical approach, define testing scenarios, and generate an issue including a conversation link for context.

Advanced Tips

Include links to design mockups or specifications in the issue body. Use GitHub task lists for sub-tasks. Apply consistent labels for filtering and organization. Mention relevant team members for awareness. Link related issues for context. Generate issues via GitHub API for automation.

When to Use It?

Use Cases

Feature planning and roadmap execution. Product requirement translation. Open source feature request handling. Sprint planning preparation. Cross-team project coordination. Developer onboarding with clear tasks. Backlog organization and maintenance.

Related Topics

GitHub project management. Agile story writing best practices. Technical specification documentation. Issue tracking and workflow automation. Development process standardization.

Important Notes

Requirements

Clear feature specification or requirement description. Understanding of technical implementation context. Access to create GitHub issues. Knowledge of team labeling and milestone conventions. Awareness of related existing issues or features.

Usage Recommendations

Review generated issues before creating for accuracy. Adjust technical approach based on codebase specifics. Add relevant labels and milestones for tracking. Link related issues and pull requests. Mention appropriate team members for visibility. Break very large features into multiple issues. Update issues as requirements evolve.

Limitations

Quality depends on specification completeness. Cannot account for undocumented technical constraints. May miss project-specific conventions without context. Requires validation by developers familiar with the codebase. Generated task breakdowns are suggestions needing refinement. Cannot replace technical design discussions.