speckit-taskstoissues

Convert spec-kit tasks into dependency-ordered GitHub issues.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/alienstro/mediapipe-scroll --skill speckit-taskstoissues-alienstro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/alienstro/mediapipe-scroll/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/alienstro/mediapipe-scroll --skill speckit-taskstoissues-alienstro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts existing spec-kit tasks into ready-to-track GitHub issues with a dependency-ordered plan, reducing manual project wrangling and ensuring the right work gets surfaced first.

Core Features & Use Cases

  • Dependency-ordered issue creation: Creates GitHub issues for tasks in the order implied by task dependencies, improving clarity for execution planning.
  • Integration with design artifacts: Builds issue content based on the available design artifacts produced by the spec-kit workflow.
  • Guardrails and hooks: Runs prerequisite checks, verifies the Git remote is a GitHub URL, and supports before/after conversion extension hooks from .specify/extensions.yml.

Quick Start

Run the speckit-taskstoissues command in your spec-kit project so it converts the current tasks into GitHub issues after validating prerequisites and the remote 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 automatically?

You can convert spec-kit tasks into GitHub issues by running a conversion command that reads your .specify directory layout and creates dependency-ordered issues directly on your GitHub remote.

How are task dependencies handled when creating GitHub issues from spec-kit?

Task dependencies are handled by creating GitHub issues in a dependency-ordered sequence, ensuring prerequisite work is surfaced first to improve execution planning and clarity.

Do I need a specific Git remote setup to generate GitHub issues from spec-kit tasks?

Yes, a GitHub remote is required because the conversion process enforces strict GitHub-remote URL validation before it can generate any issues from your spec-kit tasks.

What prerequisites are checked before turning spec-kit tasks into GitHub issues?

Prerequisites checked include task discovery via the check-prerequisites PowerShell script and verification of available design artifacts within the .specify directory.

Can I run custom scripts before or after converting spec-kit tasks to GitHub issues?

Yes, you can run custom scripts by defining before and after conversion extension hooks within the .specify/extensions.yml file to execute during the issue creation workflow.