speckit-taskstoissues

Convert Speckit feature tasks into dependency-ordered GitHub issues.

1|Updated May 20, 2026
One-click install
npx skills add https://github.com/sabrydawood/claude-config --skill speckit-taskstoissues-sabrydawood
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/sabrydawood/claude-config/tree/main/skills/speckit-taskstoissues
Command: npx skills add https://github.com/sabrydawood/claude-config --skill speckit-taskstoissues-sabrydawood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts existing Speckit tasks into actionable GitHub issues that reflect dependency order, so you can track implementation work without manually reorganizing artifacts.

Core Features & Use Cases

  • Dependency-ordered issue creation: Transforms tasks into a sequence that respects dependencies for a feature based on available design artifacts.
  • Speckit-structure aware: Extracts required paths from a spec-kit style repository with a .specify directory.
  • Safe GitHub target validation: Refuses to create issues unless the detected git remote is a GitHub URL.
  • Use Case: You have a feature’s tasks defined in Speckit, and you want GitHub issues created so your team can execute the work in the right order.

Quick Start

Run speckit-taskstoissues with an optional filter or label to create GitHub issues for the feature tasks in dependency order, for example: "Create issues for all tasks labeled api using my Speckit spec structure."

Frequently Asked Questions about speckit-taskstoissues

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

FAQPage Schema
How do I convert Speckit tasks into GitHub issues?

Dependency-ordered issue creation transforms Speckit feature tasks based on available design artifacts into a sequence that respects task dependencies, ensuring execution order is maintained.

Can I filter which Speckit tasks become GitHub issues by label?

Yes, you can optionally filter Speckit tasks by label or other user-provided criteria before generating GitHub issues, allowing targeted creation for specific task subsets.

What repository structure is required to generate GitHub issues from Speckit?

Generating GitHub issues from Speckit requires a spec-kit structure repository containing a .specify directory with available design artifacts for proper task extraction.

Does the issue creation process validate the GitHub remote URL?

Yes, the issue creation process validates the git origin remote and refuses to create issues unless the detected remote is confirmed to be a GitHub URL.

Why are my Speckit tasks not converting into ordered GitHub issues?

Speckit tasks may fail to convert if the prerequisites checker cannot extract the feature directory, the git origin remote is not a valid GitHub URL, or the .specify directory structure is missing.