speckit-taskstoissues

Convert design artifacts and tasks into dependency-ordered GitHub issues.

Updated May 16, 2026
One-click install
npx skills add https://github.com/WeihanLi/Spark.OpenXml --skill speckit-taskstoissues-weihanli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-taskstoissues
Source: https://github.com/WeihanLi/Spark.OpenXml/tree/main/.agents/skills/speckit-taskstoissues
Command: npx skills add https://github.com/WeihanLi/Spark.OpenXml --skill speckit-taskstoissues-weihanli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert existing tasks and design artifacts into actionable, dependency-ordered GitHub issues to streamline feature development and planning.

Core Features & Use Cases

  • Automatically transform design artifacts and task lists into sequenced issues for sprints.
  • Enforce dependencies and ordering to reflect feature work priorities.
  • Use case: When you have a design spec and a backlog, generate a ready-to-work issue plan for the next milestone.

Quick Start

Convert your design artifacts and tasks into a prioritized 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 turn design specs into GitHub issues for sprint planning?

You can convert design artifacts and task lists into GitHub issues by applying spec-driven workflows to generate prioritized, ready-to-work issue plans for your next milestone.

How do I automate dependency ordering for multi-issue feature development in GitHub?

You can automate dependency ordering by transforming design artifacts into sequenced GitHub issues that enforce project-scoped rules and reflect feature work priorities.

Can I generate a backlog of GitHub issues from an existing design document?

Yes, you can read design sources to automatically transform project tasks and design artifacts into actionable, dependency-ordered GitHub issues for organized feature work.

What is the best way to structure a multi-issue feature plan from a project spec?

The best way to structure a multi-issue feature plan is to enforce dependencies and ordering across your backlog to produce well-ordered issues that reflect feature work priorities.

How are input validation errors handled when generating GitHub issues from tasks?

Input validation and error handling are enforced during the transformation process to ensure project-scoped rules are met when producing well-ordered issues from design sources.