speckit-workflows.phasestoissues

Convert development phases from specification files into GitHub issues with task sub-issues.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/refactory-lang/refactory-template --skill speckit-workflows-phasestoissues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-workflows.phasestoissues
Source: https://github.com/refactory-lang/refactory-template/tree/main/.claude/skills/speckit-workflows.phasestoissues
Command: npx skills add https://github.com/refactory-lang/refactory-template --skill speckit-workflows-phasestoissues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines project management by automatically converting development phases defined in your project's specification files into detailed GitHub issues, complete with tasks as sub-issues.

Core Features & Use Cases

  • Automated Issue Creation: Generates GitHub issues directly from project phases.
  • Task Breakdown: Converts tasks from tasks.md into individual, trackable sub-issues.
  • Contextual Information: Enriches issues with descriptions, acceptance criteria, and implementation plans from specification files.
  • Labeling: Automatically applies relevant labels based on workflow type and priority.
  • Use Case: After defining a new feature in your spec.md and breaking down the work in tasks.md, run this Skill to create a parent GitHub issue for the phase and individual sub-issues for each task, ready for your team to pick up.

Quick Start

Use the speckit-workflows.phasestoissues skill to convert the current development phase into GitHub issues.

Frequently Asked Questions about speckit-workflows.phasestoissues

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

FAQPage Schema
How do I convert development phases into GitHub issues?

This Skill converts development phases from specification files into GitHub issues. It reads phase definitions and automatically generates parent issues complete with tasks as sub-issues for structured agile tracking.

Can I automatically create GitHub sub-issues from tasks.md?

Yes, you can automatically create GitHub sub-issues from tasks.md. The Skill parses task breakdowns and converts each individual task into a trackable sub-issue linked under the parent phase issue.

What project specification files are required to generate GitHub issues?

Generating GitHub issues requires access to project specification files, specifically spec.md, plan.md, and tasks.md. The Skill reads these files to extract descriptions, acceptance criteria, and implementation plans.

Does this workflow automation apply agile labels to GitHub issues?

Yes, this workflow automation applies relevant labels to GitHub issues. It automatically assigns labels based on the specific workflow type and priority defined within your project specification files.

How do I link GitHub issues to my existing Git repository information?

To link GitHub issues to your Git repository, the Skill requires Git repository information during creation. It uses this repository context to ensure generated phase issues and sub-issues are correctly associated.