speckit-taskstoissues

Convert backlog specs into dependency-ordered GitHub issues with linked design artifacts.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/ericstiles/spec-kit-backlog --skill speckit-taskstoissues-ericstiles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/ericstiles/spec-kit-backlog/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/ericstiles/spec-kit-backlog --skill speckit-taskstoissues-ericstiles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Backlog items often remain vague and untracked, delaying implementation. This Skill converts backlog specs into concrete, dependency-aware GitHub issues that can be scheduled and linked to design artifacts.

Core Features & Use Cases

  • Convert backlog specs into actionable GitHub issues with linked design artifacts.
  • Respect dependencies and ordering to drive incremental implementation.
  • Use case: promote backlog items to active issues once design artifacts are ready.

Quick Start

Create GitHub issues from all backlog items in specs/backlog using the available design artifacts as references.

Frequently Asked Questions about speckit-taskstoissues

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

FAQPage Schema
How do I convert backlog specs into GitHub issues automatically?

Backlog items are transformed into actionable GitHub issues by reading specs/backlog files, validating the GitHub remote URL, and using the MCP server to create dependency-ordered issues linked to existing design artifacts.

Does converting backlog tasks to GitHub issues require a specific repository setup?

Yes, this task requires a Git repository with a GitHub remote configured. The process validates the remote URL is GitHub and only creates issues in the matching repository to prevent incorrect submissions.

Can I create GitHub issues from backlog items that have dependencies?

Yes, backlog items with dependencies are supported. The tool respects dependency ordering to drive incremental implementation, ensuring issues are generated in a logical sequence based on available design artifacts.

What is the best way to promote spec-kit backlog items to active GitHub issues?

The best way is to promote backlog items to active issues once design artifacts are ready. This converts vague backlog specs into concrete, dependency-aware GitHub issues that can be scheduled and linked to design artifacts.

Why does my backlog task conversion fail when my Git remote is not GitHub?

Conversion fails because the tool strictly validates that the Git remote URL points to GitHub. It only uses the MCP server to create issues in the repository that matches the remote URL, preventing creation on incompatible platforms.