speckit-workflows.phasestoissues

Convert spec-kit phases and tasks into labeled GitHub issues.

2|Updated Jan 29, 2026

Search Tags:#automation #planning #github #issues #speckit #phases #workflows

Ready to run

npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-workflows-phasestoissues-pradeepmouli

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-workflows.phasestoissues
Source: https://github.com/pradeepmouli/lspeasy/tree/main/.github/skills/speckit-workflows.phasestoissues
Command: npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-workflows-phasestoissues-pradeepmouli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert development phases into individual GitHub issues for better tracking and collaboration across teams.

Core Features & Use Cases

Create a parent Phase issue capturing phase description, acceptance criteria, and implementation plan from spec-kit files.
Create individual Task issues for each task in tasks.md, linked as sub-issues to the phase issue.
Automatically apply labels based on workflow context and validate the GitHub repository remote for safe operations.
Maintain traceability by linking issues to branches and feature directories.

Quick Start

Run the Speckit workflows to generate phase and task issues from the current feature spec.

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 spec-kit phases into trackable GitHub issues?▼

Creating GitHub issues from spec-kit files involves parsing spec.md, tasks.md, and plan.md to generate a parent phase issue and individual child task issues, applying workflow labels and validating the GitHub remote for safe operations.

How does linking tasks to parent phase issues work in GitHub?▼

Linking tasks to parent phase issues works by creating a main phase issue capturing the implementation plan, then generating individual task issues from tasks.md and attaching them as sub-issues to maintain traceability and accountability.

Do I need a specific repository setup to automate GitHub issue creation from spec-kit?▼

Automating GitHub issue creation from spec-kit requires a repository leveraging the spec-kit workflow with valid spec.md, tasks.md, and plan.md files, and requires validating the GitHub repository remote to ensure safe operations.

What is the best way to structure GitHub issue bodies from planning markdown files?▼

The best way to structure GitHub issue bodies from planning files is to extract the phase description, acceptance criteria, and implementation plan from spec.md and plan.md, applying appropriate workflow labels to format the output safely.

Why does automated issue generation validate the GitHub remote repository?▼

Automated issue generation validates the GitHub remote repository to satisfy safety requirements, ensuring that issues are only created in the correct linked repository and preventing accidental writes to unauthorized or incorrect targets.