speckit-taskstoissues

Convert spec tasks into dependency-ordered GitHub issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, powershell.

What problem does it solve?

It helps you convert existing spec tasks into ready-to-track GitHub issues in a dependency-ordered way, so work is easier to plan, assign, and execute.

Core Features & Use Cases

  • Dependency-ordered task conversion: Creates GitHub issues that reflect the task list returned by the repo’s prerequisite check.
  • GitHub-remote safety guard: Only proceeds when the repository remote URL is a GitHub URL to prevent accidental issue creation elsewhere.
  • Extension hook integration: Supports optional and mandatory pre/post hooks from .specify/extensions.yml, including deterministic presentation of hook commands.

Quick Start

Run speckit-taskstoissues from the spec-kit project root to convert the tasks into actionable GitHub issues for the connected GitHub repository.

Frequently Asked Questions about speckit-taskstoissues

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

FAQPage Schema
How do I convert spec-kit tasks into GitHub issues with dependency ordering?

To convert spec-kit tasks into GitHub issues, run the Skill from your project root to generate dependency-ordered issues based on the prerequisite check. It reads task artifacts from the .specify directory and creates issues reflecting the required workflow sequence.

Does the task conversion process enforce any repository safety checks?

Yes, the task conversion process enforces a GitHub-remote-only safety guard by reading the repository's origin URL. It only proceeds to create issues when the remote URL matches a GitHub repository to prevent accidental issue creation elsewhere.

Can I use extension hooks with spec-kit task conversion to GitHub issues?

Yes, you can use optional and mandatory pre/post extension hooks defined in .specify/extensions.yml. The conversion process integrates these hooks deterministically, executing commands before and after the GitHub issues are created.

What do I need to set up before converting spec tasks to GitHub issues?

You need a spec-kit project containing a .specify directory with task artifacts, a configured GitHub remote URL, and PowerShell with Git installed. The conversion relies on these repo-provided artifacts to generate the dependency-ordered issues.

Why are my spec-kit tasks not converting into GitHub issues?

Spec-kit tasks fail to convert into GitHub issues if the repository's origin URL does not match a GitHub remote. The safety guardrail blocks execution to prevent accidental issue creation on non-GitHub platforms, so verify your remote configuration.