speckit-taskstoissues

Convert Spec Kit task plans into dependency-ordered GitHub issues.

Updated May 18, 2026
One-click install
npx skills add https://github.com/KamiJeong/tech-bridge-book --skill speckit-taskstoissues-kamijeong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/KamiJeong/tech-bridge-book/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/KamiJeong/tech-bridge-book --skill speckit-taskstoissues-kamijeong

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill converts an existing task list into clear, actionable GitHub issues so teams can move from planning artifacts to execution without manual reformatting.

Core Features & Use Cases

  • Task Breakdown: Splits feature work into individual issues that are easier to assign and track.
  • Dependency Ordering: Preserves execution order so blockers and prerequisites are handled first.
  • GitHub Integration: Creates issues in the repository that matches the current Git remote.
  • Use Case: A Spec Kit project with completed task definitions can use this Skill to turn them into a ready-to-work issue backlog for implementation.

Quick Start

Ask the skill to convert the current project tasks into GitHub issues for the active feature.

Frequently Asked Questions about speckit-taskstoissues

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

FAQPage Schema
How do I convert a task list into ordered GitHub issues?

The skill converts existing task plans into dependency-ordered GitHub issues by reading task artifacts and creating execution-ready issues in the repository matching your current Git remote.

What is dependency ordering when creating GitHub issues from tasks?

Dependency ordering preserves the execution sequence of your task plan so that prerequisite tasks and blockers are handled first when generating GitHub issues.

How do I generate GitHub issues from a Spec Kit project structure?

You can generate GitHub issues from a Spec Kit project by validating task artifacts under the .specify structure, matching the Git remote repository, and creating individual issues for each defined task.

Does this task-to-issue conversion work with any Git repository?

No, task-to-issue conversion requires repositories using task artifacts under the .specify project structure and validates that the current Git remote matches before creating GitHub issues.

What are the limitations of automating GitHub issue creation from task plans?

Automating GitHub issue creation is limited to repositories with task artifacts under the .specify structure and requires exact Git remote matching, preventing execution if prerequisites are not met.