speckit-taskstoissues

Convert spec-kit tasks into GitHub issues in dependency order.

2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill speckit-taskstoissues-d0whc3r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/d0whc3r/statsig-browser-extension/tree/main/.trae/skills/speckit-taskstoissues
Command: npx skills add https://github.com/d0whc3r/statsig-browser-extension --skill speckit-taskstoissues-d0whc3r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you convert existing spec-kit tasks into GitHub issues that are ready to execute in the correct dependency order, so teams can track progress and collaborate without manually creating or sequencing issues.

Core Features & Use Cases

  • Dependency-ordered issue generation: Creates one GitHub issue per task, using the tasks list produced by the repo’s prerequisite script.
  • Safety guardrail for targets: Refuses to create issues unless the origin remote is a GitHub URL, preventing accidental writes to the wrong hosting provider.
  • Extension hook support (before and after): Runs optional or mandatory extension hooks defined in .specify/extensions.yml, with invalid YAML handled silently and condition evaluation delegated to the HookExecutor when a hook includes a condition.

Quick Start

Use the speckit-taskstoissues skill to convert the repository’s current tasks into GitHub issues by running it in the spec-kit project root and passing the inputs it requests.

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 in dependency order?

This skill converts spec-kit tasks into GitHub issues in dependency order by utilizing the task list produced by the repository's check-prerequisites script. It creates one tracked GitHub issue per task to improve execution planning and team collaboration.

What prerequisites do I need to generate GitHub issues from spec-kit tasks?

Generating GitHub issues from spec-kit tasks requires a repository with a spec-kit project structure. You must first run the check-prerequisites script with task and document discovery to produce the task list, and verify that your origin remote points to a GitHub URL.

Why does spec-kit issue generation refuse to create issues for my repository?

Spec-kit issue generation refuses to create issues if your repository's origin remote does not match a GitHub URL. This safety guardrail prevents accidental writes to the wrong hosting provider, ensuring issues are only created when the remote is verified as GitHub.

Does converting spec-kit tasks to GitHub issues support custom automation hooks?

Converting spec-kit tasks to GitHub issues supports optional or mandatory extension hooks defined in `.specify/extensions.yml`. It runs before and after hooks, handles invalid YAML silently, and delegates condition evaluation to the HookExecutor when a hook includes a condition.

Can I use spec-kit task tracking with Git hosting providers other than GitHub?

Spec-kit task tracking issue generation is restricted to GitHub. The skill explicitly checks the origin remote and will only create issues when the remote matches a GitHub URL, preventing accidental writes to other Git hosting providers.