speckit-taskstoissues

Convert task lists and design artifacts into dependency-ordered GitHub issues.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/xyphyx/internal-project-template --skill speckit-taskstoissues-xyphyx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/xyphyx/internal-project-template/tree/main/.claude/skills/speckit-taskstoissues
Command: npx skills add https://github.com/xyphyx/internal-project-template --skill speckit-taskstoissues-xyphyx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This capability addresses the challenge of turning scattered tasks and design artifacts into a structured backlog by generating ordered GitHub issues that reflect task dependencies.

Core Features & Use Cases

  • Dependency-aware conversion of tasks to GitHub issues.
  • Design-driven prioritization and automatic ordering.
  • End-to-end GitHub issue creation and linking to design artifacts.
  • Use Case: When a feature design is available, Speckit creates issues for UI, backend, and tests in the correct order for sprint planning.

Quick Start

Provide your task list and design artifacts to generate an ordered set of GitHub issues ready for sprint planning.

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 task list into ordered GitHub issues from design artifacts?

To convert tasks into GitHub issues, provide your task list and design artifacts to generate a dependency-ordered issue set. This ensures issues are created in the correct sequence for sprint planning.

Can I automatically order GitHub issues by task dependencies during feature development?

Yes, GitHub issues can be automatically ordered by task dependencies. The system analyzes your task list and design artifacts to create a prioritized issue sequence for sprint planning.

What is the best way to create GitHub issues from a feature design for sprint planning?

The best way to create GitHub issues from feature designs is using design-driven prioritization. This converts tasks and design artifacts into a dependency-ordered backlog for sprint planning.

Do I need existing design artifacts to generate dependency-aware GitHub issues?

Yes, existing design artifacts and a task list are required to generate dependency-aware GitHub issues. These inputs drive automatic ordering and issue creation in your target GitHub repository.

Why does design-driven prioritization matter when creating GitHub issues?

Design-driven prioritization matters because it ensures GitHub issues are created in the correct order for sprint planning. It aligns tasks with design artifacts, resolving dependency constraints across UI, backend, and test tasks.

How does Speckit extract tasks from the .specify project structure?

Speckit extracts tasks from the .specify project structure by reading your existing task list and design artifacts. It then converts these inputs into a dependency-ordered set of GitHub issues for feature development.