Gen Specs As Issues

Feature specifications in documents need transformation into tracked GitHub issues for team execution. This skill converts specification documents into structured GitHub issues with clear scope, acceptance criteria, technical details, and task breakdown enabling systematic feature development with proper tracking and accountability.

What Is This?

Overview

Gen Specs As Issues parses feature specifications to generate GitHub issues. It extracts requirements from specification documents, creates parent tracking issues for features, generates sub-task issues for implementation steps, defines acceptance criteria per issue, adds appropriate labels and milestones, links related issues, and formats using GitHub templates.

The skill understands specification formats including user stories, technical requirements, and product briefs. Generated issues maintain traceability between specifications and implementation work, ensuring nothing gets lost between planning and execution.

Who Should Use This

Product managers translating specs to tasks. Engineering managers planning sprints. Technical leads breaking down features. Development teams tracking work. Project coordinators managing delivery. Agile teams organizing backlogs.

Why Use It?

Problems It Solves

Manual issue creation from specs is tedious and inconsistent. Automated generation ensures complete coverage of requirements without relying on individual memory or interpretation.

Specifications remain disconnected from implementation tracking. Generated issues link specifications directly to development work.

Task breakdown requires technical understanding. The skill suggests reasonable work division based on specification details.

Acceptance criteria get lost in translation. Issues include explicit criteria extracted from specifications.

Core Highlights

Specification parsing. Parent issue generation. Sub-task breakdown. Acceptance criteria extraction. Label assignment. Milestone linking. Issue relationship mapping. Template formatting.

How to Use It?

Basic Usage

Provide feature specification document or text. The skill generates GitHub issues ready for creation with proper structure.

Convert feature spec to GitHub issues
[Provide specification document]

Generate issues from product requirements
with task breakdown and acceptance criteria

Specific Scenarios

For large features, create epic with sub-tasks.

Generate parent epic issue with linked
sub-issues for each implementation phase

For sprint planning, include estimates.

Create issues with complexity labels
and sprint milestone assignments

For team coordination, specify assignments.

Generate issues tagged for frontend,
backend, and QA team members

Real World Examples

A product manager writes specification for user authentication feature covering registration, login, password reset, and profile management. Converting manually to issues takes hours. Generated issues include parent epic tracking overall authentication system, registration sub-issue with form requirements and validation criteria, login sub-issue covering session management, password reset sub-issue with email workflow, profile management sub-issue with update functionality, and appropriate labels like feature and security. Development proceeds with clear task structure.

A technical lead receives vague specification requiring implementation details. Issue generation extracts clear requirements, identifies missing technical details through questions, creates issues for each component, defines API contracts needing specification, includes testing requirements, and flags dependency on infrastructure work. Team has actionable issues despite initial specification gaps.

An engineering manager plans quarterly roadmap with multiple feature specifications. Manual issue creation is bottleneck. Batch processing generates issues for all features, organizes with quarterly milestones, assigns appropriate labels, creates dependency links between features, includes acceptance criteria from specs, and produces issue list for sprint planning. Roadmap execution begins immediately with proper tracking.

Advanced Tips

Use consistent issue templates across all generated work. Link issues back to the original specification documents for full traceability. Apply labels systematically to support filtering and reporting. Set realistic milestones aligned with team capacity. Include testing requirements within each issue rather than as separate afterthoughts. Flag dependencies explicitly so teams can sequence work correctly. Provide enough detail for independence. Update issues as specs evolve.

When to Use It?

Use Cases

Sprint planning preparation. Feature requirement tracking. Roadmap execution. Product development workflow. Team task assignment. Progress reporting. Specification traceability. Backlog organization.

Related Topics

Agile user story writing. GitHub project management. Requirement decomposition. Task estimation. Issue tracking workflows. Sprint planning. Acceptance criteria definition.

Important Notes

Requirements

Clear specification documents. GitHub repository access. Understanding of team workflow. Issue template definitions. Label and milestone structure. Team capacity awareness.

Usage Recommendations

Review generated issues before creation. Adjust breakdown for team capacity. Validate acceptance criteria completeness. Link to specification source. Assign appropriate owners. Set realistic milestones. Include technical dependencies. Update as requirements change.

Limitations

Quality depends on specification clarity. Cannot resolve ambiguous requirements. May need manual adjustment. Requires validation by technical team. Should adapt to team practices.