speckit-taskstoissues

Convert project task lists into dependency-ordered GitHub issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert existing tasks into actionable, dependency-ordered GitHub issues for a feature based on available design artifacts.

Core Features & Use Cases

  • Automatically generate GitHub issues from a task list, preserving dependencies and design references.
  • Organize work items into a coherent, dependency-driven backlog that maps to design artifacts.
  • Use case: Given a spec-kit style project with a .specify/ directory, generate issues that reflect required tasks and their relationships.

Quick Start

Provide your project task list and design artifacts, then run speckit taskstoissues to generate GitHub issues ordered by dependencies.

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 project task list into dependency-ordered GitHub issues?

You can convert a project task list into dependency-ordered GitHub issues by providing your task list and design artifacts, which generates issues reflecting task dependencies and design references via the GitHub MCP server.

What are dependency-ordered GitHub issues and when do I need them?

Dependency-ordered GitHub issues are backlog items organized by their required relationships and design references. You need them when converting a spec-kit task list into an actionable, dependency-driven sequence for feature development.

Does this task conversion require a specific project directory structure?

Yes, this task conversion requires a spec-kit style project structure containing a .specify/ directory with templates. It also reads .specify/extensions.yml hooks for pre- and post-execution steps during the issue generation process.

Can I use this to generate GitHub issues from local design artifacts automatically?

Yes, you can generate GitHub issues from local design artifacts by running the conversion process. It determines the Git remote from your repository and creates issues while ensuring the remote URL matches before proceeding.

What is the best way to organize a task backlog that maps to design artifacts in GitHub?

The best way to organize a task backlog that maps to design artifacts is to convert existing tasks into dependency-ordered GitHub issues. This creates a coherent backlog reflecting required tasks and their relationships based on your design artifacts.

Why does GitHub issue generation fail when my Git remote URL does not match?

GitHub issue generation fails when the Git remote URL does not match because the system validates the remote URL before creating issues via the GitHub MCP server, ensuring tasks are pushed to the correct repository.