speckit-phasestoissues

Create GitHub phase issues and linked task sub-issues from spec.md and tasks.md.

2|Updated Jan 29, 2026

Search Tags:#automation #github #issues #speckit #spec-kit #phasestoissues

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating large development efforts is hard; speckit-phasestoissues turns each defined development phase into a dedicated GitHub issue to align teams and track progress.

Core Features & Use Cases

Decompose a feature into Phase issues from spec-kit structure (spec.md, tasks.md, etc).
Automatically assemble a comprehensive phase body including description, acceptance criteria, implementation plan, decisions, and dependencies.
Create sub-issues for each task in the phase and link them to their parent phase issue for traceability.
Provide guidance to attach issue links to branches and commit messages for easy traceability.
Edge-case handling: no tasks.md or no spec.md produce sensible fallbacks and notes.

Quick Start

Run speckit-phasestoissues in a repository that follows the spec-kit workflow to generate phase-level issues from spec.md and tasks.md.

Frequently Asked Questions about speckit-phasestoissues

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

FAQPage Schema

How do I convert development phases into GitHub issues?▼

Yes, you can automate GitHub issue creation from spec-kit files. The Skill parses spec.md for phase definitions and tasks.md for task lists, automatically generating linked parent and sub-issues via the GitHub MCP server with proper labeling to align team coordination.

What is the best way to track spec-kit phases on GitHub?▼

To use this Skill, your repository must follow the spec-kit workflow with a spec.md defining feature phases and a tasks.md listing per-phase tasks. A valid GitHub remote must be configured to validate and create the issues through the MCP server.

How does issue generation handle missing spec.md or tasks.md files?▼

When spec.md or tasks.md files are missing during issue generation, the Skill applies sensible fallbacks and generates notes. It handles these edge cases gracefully rather than failing, ensuring the automation completes with available feature context.

How do I link GitHub issues to branches and commits for spec-kit tracking?▼

To link GitHub issues to branches and commits, the Skill provides guidance on attaching the newly generated issue links to your commit messages and branch names. This ensures full traceability from code changes back to the specific development phase and tasks.